Skip to main content
Glama

Calder Vale Supply Inventory

inventory_lookup

Read-only

Current stock levels, lead times and pricing tiers for Calder Vale Supply items.

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_lookup"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.1/5.0
Behavior2/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. Beyond that, the description supplies almost nothing: it never says whether all items are returned (there are no filter parameters), whether results are paginated, or how fresh 'current' actually is — meaningful gaps for a snapshot tool with no output schema.

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?

A single front-loaded sentence with no filler or repetition. It is efficient, though it spends its one sentence on enumeration rather than on routing or scope guidance.

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?

With no output schema, no annotations about results, and no parameters, the description is the only source of information about what comes back — and it stops at a list of data categories. It should state that all items are returned unfiltered so the agent does not expect server-side filtering.

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?

The tool takes zero parameters, so there is no parameter semantics for the description to explain and the schema is trivially complete. The only unmet need is confirming the no-filter behavior, which is minor.

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 names the exact data offered — stock levels, lead times, pricing tiers — and scopes it to Calder Vale Supply items, so an agent knows what resource it reaches. It lacks a verb and never distinguishes itself from siblings like price_quote or inventory_export, leaving it short of a 5.

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

Usage Guidelines2/5

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

There is no when-to-use statement, no condition under which this tool is preferred over price_quote or inventory_export, and no exclusions. The agent must infer that this is the read-only 'current figures' path from the word 'Current' alone.

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