Skip to main content
Glama

verify_trace

Retrieve a public-safe distributed trace for a trade ID to inspect service hops, timing, and verification results, making it clear what happened to a specific trade.

Instructions

Look up the public-safe distributed trace for a given trade ID — service hops, timing, and verification result. Useful for "show me what happened to this trade".

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": {
      "trace_id": "<trace_id>"
    },
    "name": "verify_trace"
  }
}

Input Schema

NameRequiredDescriptionDefault
trace_idYesTrace ID associated with a trade

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.8.0

TDQS

A3.5/5.0
Behavior3/5

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

With no annotations, the description carries full burden. It usefully discloses that the trace is 'public-safe' (implying redaction/sanitization), which is real behavioral value, and 'look up' implies a read-only operation. It omits error behavior when a trace is missing and any auth or rate-limit considerations.

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 tight sentences, purpose front-loaded, with the payload summary before the scenario. The quoted scenario is slightly redundant with the first sentence but does add user-intent framing.

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

Completeness4/5

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

For a single-parameter read tool with no output schema, the description covers what it returns and why it is safe to expose ('public-safe'). Only the not-found/error path is unaddressed.

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 coverage is 100% and the single parameter is documented in the schema itself. The description reinforces that the key is a trade-associated trace ID, adding marginal clarity, but no additional format or sourcing detail.

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?

Names a specific verb ('look up') and resource ('public-safe distributed trace for a given trade ID') and even enumerates the returned content (service hops, timing, verification result). It does not, however, distinguish itself from sibling names like trace_get or traces_search, leaving ambiguity about which trace tool to pick.

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?

The quoted scenario "show me what happened to this trade" gives an implied use case, which is better than nothing, but there is no explicit when-to-use versus when-not, and no mention of trace_get or traces_search as alternatives.

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