Skip to main content
Glama

Proof of delivery

get_proof_of_delivery
Read-onlyIdempotent

Signed photo URLs (1h), signature, recipient name, geo + time.

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": {
      "delivery_id": "<delivery_id>"
    },
    "name": "get_proof_of_delivery"
  }
}

Input Schema

NameRequiredDescriptionDefault
delivery_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3/5.0
Behavior4/5

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

Annotations already establish read-only, idempotent, non-destructive behavior, so the bar is lower. The description adds a genuinely useful behavioral detail: photo URLs are signed and expire after one hour, which affects how the caller should handle the returned links. It still omits availability behavior when no POD exists, but it adds clear value beyond the annotations.

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?

The definition is extremely short with no filler, and the most operationally important detail, the one-hour signed URL expiry, is included. However, the fragmentary list structure and abbreviations like 'geo + time' make it less immediately readable than a concise sentence would be.

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 single-parameter read tool, the description gives useful return-content detail in the absence of an output schema. It is still incomplete on parameter meaning and on what happens when proof of delivery is unavailable, so an agent lacks some information needed to call and interpret it confidently.

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 0% and the only parameter, delivery_id, is not mentioned or clarified in the description. The parameter name is self-explanatory, but the description contributes no meaning about the identifier's expected format or scope.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description is a telegraphic list of returned artifacts rather than a verb-led statement of what the tool does. Combined with the name 'get_proof_of_delivery' it is interpretable, but the description itself does not explicitly say it retrieves proof-of-delivery data, and it does not differentiate from siblings such as get_delivery or track_delivery.

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?

There is no when-to-use guidance, no mention of prerequisites such as a completed delivery, and no reference to alternatives. An agent must infer that this is the POD-specific retrieval tool from the name and returned-field list 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.