ClaudeskillsMCPtolls

Claude skill for calculating tolls: how to build it on the API

A Claude skill adds toll know-how, but needs a real transport (MCP or scripted HTTP calls) to reach the toll API; structure, example and limits.

By Jorge Parada, CTO de Cargoffer

Claude skill for calculating tolls

Direct answer: a Claude skill is a folder of instructions (plus optional scripts) that teaches Claude how to do a task with the tools it already has. For tolls, the skill itself adds no network access: you still need a real channel to the API β€” the documented MCP server or script execution with network. The skill encodes know-how: which endpoint, which vehicle class, how to present the breakdown and mark results as estimates.

Skill vs MCP

  • Claude with tools (Claude Code locally, or Claude Desktop with the MCP integration): the skill works as the procedure layer on top.
  • Plain Claude chat without tools: a skill cannot call the API; set up MCP first.

Minimal structure

skills/tolls-calculator/SKILL.md with the workflow (ask origin/destination or polyline; call POST https://back.transcend.cargoffer.com/api/v1/tolls/calculate through the available tool; present per-section results with query date; never state a price without a live call) plus an optional scripts/ curl helper. The API key lives in environment variables β€” never inside the skill file.

This is an integration pattern you build; no official published skill is claimed.

Frequently asked questions

Can a Claude skill query the toll API by itself?
No. The skill is instructions; the live call runs through a networked tool (MCP or scripts) using your key.
What transport do you recommend for Claude?
The documented MCP server (@cargoffer/mcp-server-transcend) in Claude Desktop or Claude Code, with the skill as the procedure layer.
Where does the API key go?
Local environment variables of the machine running the call; never in the skill file or prompt.

Related resources

Ready to calculate tolls with live data?