Skip to main content
Glama

Calder Vale Supply Inventory

inventory_export

Read-only

Staff-only operation requiring separate written approval. Public client access does not authorize it.

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": "inventory_export"
  }
}

Input Schema

NameRequiredDescriptionDefault
approval_refNoWritten approval reference issued by Calder Vale Supply staff.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.7/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is covered. The description adds a meaningful prerequisite the annotations do not carry (staff role plus a written approval reference), which is exactly the kind of context that matters here. It does not, however, describe what the operation returns or how the approval is validated.

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?

Two sentences with zero filler, so nothing is wasted. But the front-loaded content is the access restriction rather than the tool's purpose, which is the wrong ordering for an agent deciding whether to call it.

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?

For a one-parameter read-only tool with no output schema, the description should at minimum say what is exported and over what scope. It omits the operation entirely, so an agent cannot judge suitability even though the schema and annotations are otherwise tidy.

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% and the single approval_ref parameter is fully documented in the schema, including that it is issued by Calder Vale Supply staff. The description restates the approval requirement without adding format, validation, or sourcing detail beyond the schema, so the baseline 3 applies.

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

Purpose2/5

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

The description never states what the tool does. It only communicates an access gate ('Staff-only operation requiring separate written approval'), leaving the agent to infer 'export inventory' from the name alone. It does not distinguish this from siblings like inventory_lookup or price_quote in terms of what operation is performed.

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?

There is real when-not-to-use guidance: public client access does not authorize invocation, and written approval is required. However, no alternative tool or path is named for callers who lack approval, and no positive condition ('use this to obtain a full inventory extract') is stated.

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