Skip to main content
Glama

Provanza delivery evidence

lookup_carrier_evidence

Read-only

Look up a documented carrier, market, and service example. Returns the issuer, evidence provenance, input requirements, availability guidance, and sources. The directory does not determine whether a particular shipment has proof.

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": {
      "carrier": "<carrier>"
    },
    "name": "lookup_carrier_evidence"
  }
}

Input Schema

NameRequiredDescriptionDefault
localeNo
carrierYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false; the description corroborates this by describing a fixed directory with enumerated carriers and explicitly disclaiming proof-of-shipment authority. It also lists the returned fields, which matters because there is no output schema. It stops short of describing result limits, paging, or what happens when a carrier has no documented example.

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?

Three front-loaded sentences with no filler: what it does, what it returns, what it does not do. The phrase "carrier, market, and service example" is slightly compressed and leaves the relationship between those three things and the two input parameters unclear.

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?

The return-field enumeration compensates for the missing output schema, and the disclaimer covers the main misuse risk. For a two-parameter lookup tool, though, the unexplained `locale` parameter and the absence of guidance on how to interpret results (e.g., what a partial or empty example set means) leave real gaps.

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 description never explains either parameter. The word "carrier" loosely maps to the required carrier field, but the `locale` parameter and its four enum values are entirely unaddressed, as is the special "delivered-evidence" carrier value. With near-zero schema coverage, the description should have compensated and does not.

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?

The description opens with a specific verb+resource: "Look up a documented carrier, market, and service example," and then enumerates what the lookup returns (issuer, provenance, requirements, availability, sources). An agent can tell this is a read-only reference-directory tool rather than a verification tool. It does not explicitly contrast with the only sibling, run_fictional_pod_demo, but the two purposes are plainly disjoint.

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 rather than stated: "documented... example" signals reference browsing, and the closing sentence gives a genuine exclusion ("does not determine whether a particular shipment has proof"). However, no positive when-to-use condition and no named alternative for the verification task are provided, so the agent must infer the routing.

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