Skip to main content
Glama
Tarmac MCP

Tarmac MCP

Official
by tarmacagent

Get a swap quote

tarmac_get_quote
Read-only

Fetches a swap quote between two tokens, returning the expected output amount, reference mid price, and slippage in BPS so you can check slippage against your policy limit before swapping.

Instructions

Quote tokenIn → tokenOut. Returns quoteId, amountOut, the reference (mid) output and slippageBps. Compare slippageBps to the policy limit before swapping.

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": {
      "tokenIn": "<tokenIn>",
      "tokenOut": "<tokenOut>",
      "amountIn": "<amountIn>"
    },
    "name": "tarmac_get_quote"
  }
}

Input Schema

NameRequiredDescriptionDefault
tokenInYes
amountInYes
tokenOutYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.7/5.0
Behavior4/5

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

Annotations only declare readOnlyHint=true, so the description carries useful extra weight by disclosing the exact returned fields and the policy-limit check the agent must perform. It still omits important quote behavior such as whether quotes expire or how long they remain valid, which matters before committing to a swap.

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

Conciseness5/5

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

Three short sentences, front-loaded with the operation, then the return payload, then the required follow-up check. No filler and no repetition of the title.

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?

With no output schema, the description does well to enumerate return fields, and it flags the slippage policy step. However, for a quoting tool it leaves out amountIn unit semantics and quote validity/expiry, both of which an agent needs to call it correctly and safely.

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

Parameters3/5

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

Schema description coverage is 0%, so the description must compensate, and it only partly does: it names tokenIn and tokenOut and implies amountIn is the input amount. It never clarifies that amountIn is a base-unit integer string matched to tokenIn's decimals, which is the single most error-prone aspect of quoting, so the schema patterns still do most of the work.

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?

The description uses a specific verb-plus-resource formulation ('Quote tokenIn → tokenOut') and immediately enumerates what comes back (quoteId, amountOut, reference mid, slippageBps). It implicitly separates itself from tarmac_request_swap by framing itself as the pre-swap check, though it never names the sibling directly.

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?

Guidance is implied through sequencing ('Compare slippageBps to the policy limit before swapping'), which tells the agent this is a read step preceding a swap. There is no explicit statement of when not to use it, no mention of the alternative tool by name, and no note about required prerequisites such as a run context.

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