Skip to main content
Glama

read_assigned_operation_evidence

Read redacted operation evidence, including result hash, settlement record, and delivery receipt summaries. Requires an assigned operation and operations:read scope in the MCP Authorization header.

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": {
      "operationId": "<operationId>"
    },
    "name": "read_assigned_operation_evidence"
  }
}

Input Schema

NameRequiredDescriptionDefault
operationIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / additionalProperties
      Added value: +false
  2. First observed

TDQS

B3.3/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 behavioral burden. It usefully discloses that evidence is redacted, lists the kinds of records returned, and states the auth scope and assignment requirement. It still omits behavior for missing evidence, not-found operations, authorization failures, and whether the read has any side effects, though "Read" implies a safe operation.

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 sentences, both front-loaded and purposeful. The first defines what is returned; the second states prerequisites. No redundant or 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 one-parameter read tool without an output schema or annotations, the description covers returned evidence categories and the authorization prerequisite. It leaves notable gaps around operationId semantics, missing/not-found evidence behavior, and how this read differs from sibling read operations.

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?

The sole required parameter, operationId, has 0% schema description coverage, so the description should compensate. It mentions an "assigned operation" requirement, which adds a constraint, but it never names operationId or explains that the parameter identifies that assigned operation. The agent must infer the parameter meaning from the schema alone.

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 and resource: "Read redacted operation evidence." It also enumerates the evidence contents (result hash, settlement record, delivery receipt summaries), making the purpose concrete. It does not explicitly distinguish this tool from sibling reads such as read_assigned_delivery_receipts or read_work_ticket_result.

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?

States prerequisites: the operation must be assigned and the caller needs operations:read scope in the MCP Authorization header. However, it gives no guidance on when to choose this tool over sibling read tools or when evidence may be unavailable. Usage is implied by the prerequisites rather than explicitly directed.

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