Skip to main content
Glama

Migawari

Get task evidence

get_evidence
Read-only

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.3/5.0
Behavior3/5

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

Annotations already establish this as a safe read (readOnlyHint=true, destructiveHint=false), so the bar is lower. The description does add a real behavioral fact — evidence is still returned for failed tasks — but omits what an empty or missing-evidence response looks like and whether the access_token scope limits results.

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?

Two short sentences, front-loaded with the core action and followed by the single most decision-relevant behavioral caveat. No filler 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 annotations covering safety and no output schema, the description covers the essentials but leaves gaps: how to obtain task_id, what the returned evidence structure contains, and whether failed tasks return partial evidence. Adequate but not complete.

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 only 50%: access_token is documented in-schema as coming from request_quote, but task_id has no description. The description says nothing about either parameter, so it fails to compensate for the undocumented task_id or clarify where a task_id originates.

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 enumerates content types (photos, records, tracking numbers), which is concrete. It does not explicitly distinguish itself from siblings like get_task_status, but 'evidence' is a distinct resource an agent can map to its intent.

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?

Usage is implied by the name and the note that evidence is returned for failed tasks, which hints at a valid call condition. There is no explicit when-to-use versus alternatives, no mention of prerequisites such as when an access_token becomes available, and no guidance on calling before vs after task completion.

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.