Skip to main content
Glama

get_evidence

Get evidence attached to a task (photos, records, tracking numbers). Evidence is returned even for failed tasks.

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": {
      "task_id": "<task_id>",
      "access_token": "<access_token>"
    },
    "name": "get_evidence"
  }
}

Input Schema

NameRequiredDescriptionDefault
task_idYes
access_tokenYesThe access_token returned by request_quote.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3/5.0
Behavior3/5

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

With no annotations, the description carries the full disclosure burden and does add one genuinely non-obvious trait: evidence is returned even for failed tasks. It omits other behavioral facts an agent would want, such as whether the call is read-only, whether the access_token must be fresh, and what happens when a task has no attachments.

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 short sentences, front-loaded with the core action and its payload examples, with zero filler. Slightly clipped grammar in the second sentence but no wasted wording.

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 simple two-parameter read tool with no output schema, the description covers what is returned in general terms but not the shape, count, or pagination of results, nor error behavior for invalid task_id. Adequate but with clear gaps given that no annotations or output schema exist to backfill.

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?

At 50% schema coverage, the description should compensate for the undocumented task_id parameter but says nothing about parameter semantics. Only access_token is described, and that documentation lives in the schema ("returned by request_quote"), not the description, so the description adds no meaning beyond structured data.

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 ("Get evidence attached to a task") and disambiguates the vague word "evidence" with concrete examples (photos, records, tracking numbers). It is clearly distinct from siblings like get_task_status or request_quote, though it never names an alternative explicitly.

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?

The description gives no when-to-use guidance and no exclusions relative to siblings such as get_task_status, which also operates on a task. The one contextual sentence ("Evidence is returned even for failed tasks") is a behavioral trait, not usage routing, so an agent must infer the selection rule from the name alone.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources