Skip to main content
Glama

read_assigned_delivery_receipts

Read signed delivery receipt proofs for an assigned operation. Requires 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_delivery_receipts"
  }
}

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 supplied, the description carries the full burden, and it usefully discloses the auth requirement ('operations:read scope in the MCP Authorization header'). It says nothing about read-only semantics, whether non-assigned operations error out, what a 'signed proof' contains, or result size/pagination.

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, zero filler, with the resource and scope front-loaded before the auth prerequisite. Nothing is wasted.

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 single-parameter read tool with no output schema, the description covers purpose and auth but leaves return shape, empty-result behavior, and permission-failure behavior unstated. Adequate to call correctly on the happy path, incomplete on the edges.

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 description coverage is 0%, so the description must compensate. 'For an assigned operation' does imply that operationId identifies an operation the caller is assigned to, adding a meaningful constraint beyond the bare uuid pattern, but it says nothing about format, sourcing, or failure behavior for an unknown/unassigned ID.

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 ('Read') and resource ('signed delivery receipt proofs') scoped to 'an assigned operation,' so it is distinguishable from a generic receipt read. It does not explicitly contrast with the nearby evidence-reading sibling, so it stops short of a 5.

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 phrase 'for an assigned operation' implies the context in which it applies, but there is no explicit when-to-use/when-not-to-use guidance and no named alternative for cases where the caller wants operation evidence rather than receipt proofs.

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