Skip to main content
Glama
Tarmac MCP

Tarmac MCP

Official
by tarmacagent

Read the run's instruction and limits

tarmac_get_context
Read-only

Fetches the active run's instruction, simulated wallet, token addresses, amount, and policy limits so agents can check swap context before requesting actions.

Instructions

Instruction, simulated wallet, token addresses, amount and policy limits for the active run.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "tarmac_get_context"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.1/5.0
Behavior3/5

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

readOnlyHint=true already covers the safety profile, and the description does add that the data pertains to the 'active run' and a 'simulated wallet', framing the sandbox context. Since there is no output schema, the field enumeration is the only disclosure of what comes back, but it stops short of explaining formats, units, or what 'policy limits' constrain.

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?

One compact fragment with no filler, and the scope ('active run') is placed at the end where it qualifies the whole list. It could be tightened into a verb-led sentence ('Returns the active run's instruction, wallet, tokens, amount and limits'), which would cost nothing.

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?

A zero-parameter read tool with annotations and no output schema is simple, and the field list partially substitutes for the missing output schema. However, terms like 'Instruction' and 'policy limits' are left undefined, so an agent cannot fully predict what it will receive or how to act on it.

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

Parameters4/5

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

The tool takes zero parameters, so the schema needs no semantic elaboration and the baseline of 4 applies. The description correctly implies no arguments are needed to target the active run.

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

Purpose3/5

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

The description is a bare noun phrase listing returned fields (instruction, simulated wallet, token addresses, amount, policy limits) scoped to 'the active run'. It conveys the resource and scope but has no verb and doesn't distinguish this from tarmac_get_run, which plausibly also reports run state; the reader must infer 'returns' from the title.

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

Usage Guidelines2/5

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

There is no when-to-use statement, no prerequisite, and no reference to any alternative among the many siblings (get_run, get_balances, get_quote). The agent can only guess that this is the first call to make at the start of a run.

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