Skip to main content
Glama

Provanza delivery evidence

run_fictional_pod_demo

Read-only

Replay a fixed fictional batch and return the three outcomes, the public fixture URL, and the marked sample PDF URL. Creates no shipment requests or charges.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "run_fictional_pod_demo"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/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, so the safety profile is partly covered. The description goes beyond them by asserting that no shipment requests or charges are created and by naming the concrete return artifacts, which is exactly the business-level reassurance an agent needs before invoking it.

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 return payload front-loaded and the safety disclaimer second. Every clause carries information an agent would otherwise have to guess.

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

Completeness4/5

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

With no output schema, the description must describe returns and does so by naming the three artifacts it produces. The only soft spot is the undefined phrase "the three outcomes," which leaves the exact result contents slightly ambiguous, but nothing needed to call the tool is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

There are zero parameters and the description correctly introduces none, so there is nothing to misinterpret. Baseline for a parameterless tool is 4; no additional input semantics are needed or missing.

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 uses a specific verb and resource ("Replay a fixed fictional batch") and enumerates what comes back: three outcomes, a public fixture URL, and a marked sample PDF URL. The word "fictional" and the explicit no-side-effect clause clearly separate it from the evidence-lookup sibling, though it never names that sibling.

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?

The description implies the context of use (a demo/sandbox replay against a fixture) and rules out any real-world effect, which is useful routing information. It does not state when an agent should prefer this over the sibling lookup_carrier_evidence, nor does it give any preconditions or exclusions.

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