Skip to main content
Glama

WritersLogic business agents

pod-sufficiency

Proof-of-delivery sufficiency against a required evidence list — Checks whether the proof-of-delivery evidence supplied (signature, photo, timestamp, GPS fix, recipient name, scan ...) satisfies the carrier or contract requirement list the caller gives: every required item, plus optional 'at least k of these' groups, with value bounds (for example GPS accuracy at most 30 m) and maximum age. For an agent assembling a delivery dispute or a payment release. Return

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": {
      "required": "<required>",
      "evidence": "<evidence>"
    },
    "name": "pod-sufficiency"
  }
}

Input Schema

NameRequiredDescriptionDefault
asOfNoReference instant (ISO date or instant) for evidence age; required only when a need sets maxAgeDays. The check never reads the clock.
anyOfNoAlternative groups: at least atLeast (default 1) of the keys must be present.
evidenceYesProof elements the caller holds.
requiredYesEvidence every proof must contain (key plus optional bounds).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/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 does disclose real semantics: every required item must be present, optional 'at least k of these' groups apply, values can be bounded (GPS accuracy at most 30 m) and evidence has a maximum age. However, it never says whether the operation is pure/non-mutating, and the trailing fragment 'Return' leaves the response behavior entirely undisclosed—a meaningful gap for an unannotated tool.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Purpose is correctly front-loaded, but the body is a single dense run-on sentence packing evidence types, group logic, bounds and age into one clause chain. Most damaging, the text ends with the dangling fragment 'Return', which suggests truncation and wastes an agent's attention on an incomplete sentence.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The tool is a checker with no output schema and no annotations, so the description should explain what the verdict looks like (per-need pass/fail, which requirements were unmet). Instead the sentence is cut off at 'Return', leaving the result shape wholly undocumented. The input side is adequately covered, but the output side—the part an agent needs to act on a dispute or payment decision—is missing.

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 coverage is 100%, so the per-parameter semantics (asOf, anyOf groups, min/max/oneOf bounds, maxAgeDays) are already documented in the schema. The description usefully synthesizes how required items and alternative groups combine, but adds no details beyond what the schema already conveys, so baseline 3 applies.

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 states a specific operation—checking proof-of-delivery evidence against a caller-supplied requirement list—and enumerates the evidence kinds (signature, photo, timestamp, GPS fix, recipient name, scan) it operates on. The verb and resource are unambiguous, so an agent knows exactly what domain this covers. It does not attempt to distinguish itself from any sibling, which keeps it just below the top mark.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It gives two concrete consumption contexts: assembling a delivery dispute or triggering a payment release. That is clear positive guidance for when to reach for the tool. There is no statement of when not to use it (e.g. no 'use X for damage claims instead') and no prerequisites, so it stops short of explicit alternatives.

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