Skip to main content
Glama

Calder Vale Supply Inventory

order_history

Read-only

Account managers only. Returns a partner's past orders and invoiced totals. 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": "order_history"
  }
}

Input Schema

NameRequiredDescriptionDefault
partnerNoPartner name or account number.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/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 real value beyond them by disclosing an authorization gate: account-manager privilege is required and public client access is insufficient, which tells the agent about likely failure modes. It still omits return shape, result volume, or pagination behavior.

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 terse sentences with the access restriction front-loaded before the capability statement. 'Public client access does not authorize it' partly restates 'Account managers only,' but it usefully rules out a specific misreading rather than being pure padding.

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

Completeness5/5

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

For a simple one-parameter read tool with full schema coverage, no output schema, and annotations carrying the safety profile, the description covers what it returns, who may call it, and the access boundary. Nothing essential to calling it correctly 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% and the single 'partner' parameter is already documented with both accepted forms (name or account number). The description adds no further meaning about the parameter, so the baseline 3 is appropriate. It also doesn't clarify what happens when the optional parameter is omitted, which would have been a useful addition.

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?

States a specific verb and resource: 'Returns a partner's past orders and invoiced totals.' An agent can distinguish this from inventory_lookup or price_quote by the resource shape, though the description never names a sibling or explicitly contrasts the scope.

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 audience constraint ('Account managers only') implies when the tool is appropriate, but there is no explicit when-to-use versus an alternative, and no stated condition like 'use when you need historical order volume rather than current stock.' Usage is implied rather than directed.

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