Skip to main content
Glama
Tarmac MCP

Tarmac MCP

Official
by tarmacagent

Request a swap

tarmac_request_swap

Request a quoted swap from a simulated wallet; every request is validated by policy checks for tokens, router, recipient, spend cap, freshness, slippage, and minimum output before execution.

Instructions

Ask Tarmac to execute a quoted swap from the simulated wallet. Every request is checked by the policy layer (tokens, router, recipient, spend cap, freshness, slippage, minimum output); a failing request is blocked and recorded.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "quoteId": "<quoteId>",
      "tokenIn": "<tokenIn>",
      "tokenOut": "<tokenOut>",
      "amountIn": "<amountIn>"
    },
    "name": "tarmac_request_swap"
  }
}

Input Schema

NameRequiredDescriptionDefault
reasonNoWhy — recorded in the trace, never used for the decision
quoteIdYes
tokenInYes
amountInYes
tokenOutYes
minAmountOutNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.4/5.0
Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations only declare idempotentHint=false and destructiveHint=false; the description adds real substance by naming the policy checks (tokens, router, recipient, spend cap, freshness, slippage, minimum output) and stating that failing requests are blocked and recorded. It still leaves the success path underspecified: no mention of what the wallet state looks like after execution or whether the swap is final.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two sentences, front-loaded with the action and followed by the enforcement behavior. The parenthetical policy list is dense but each item carries information; no filler sentences.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a state-changing tool with no output schema and mostly undocumented parameters, the definition covers the failure path well but omits the success outcome and parameter expectations. It is adequate to attempt a call but not to predict its result.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 17% — only 'reason' is documented. The description's mention of 'tokens' and 'minimum output' loosely maps to tokenIn/tokenOut/minAmountOut, but quoteId and amountIn semantics, units, and expected formats are absent, so the description does not compensate for the coverage gap.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource: execute a quoted swap from the simulated wallet. The word 'quoted' signals a dependency on a prior quote step, which implicitly separates it from tarmac_get_quote, but that sibling is never named so the differentiation is inferred rather than explicit.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

'Execute a quoted swap' implies the prerequisite of an existing quote (quoteId is required), but the description never states this condition outright or points to tarmac_get_quote as the source. There is no when-not guidance, e.g. what to do when the policy check fails.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.