Skip to main content
Glama

Check stock and dispatch window

check_stock
Read-only

USE THIS before you promise a delivery date, or when the human asks "will it arrive before X". Returns availability and the dispatch window for one SKU.

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": {
      "product_id": "<product_id>"
    },
    "name": "check_stock"
  }
}

Input Schema

NameRequiredDescriptionDefault
product_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

The readOnlyHint and openWorldHint=false annotations already declare this as a safe local read, so the bar is lower. The description adds value beyond them by disclosing the return content (availability plus dispatch window) and that the lookup is scoped to a single SKU, which is what the agent needs to reason about the result.

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 with the imperative trigger placed first and the return content second. There is no filler and nothing important is buried.

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?

For a one-parameter read tool with annotations and no output schema, the description covers when to call it and what comes back. The only remaining gap is where product_id comes from (for example, via search_products), which is a minor omission for this complexity level.

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

Parameters2/5

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

Schema description coverage is 0% and the only parameter, product_id, is undocumented in the schema. The phrase "for one SKU" hints that product_id identifies a single SKU, but it gives no format, identifier source, or lookup-failure guidance, so it only partially compensates for the coverage gap.

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

Purpose5/5

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

The description names a concrete resource (one SKU) and concrete outputs (availability and dispatch window), which is specific enough to separate it from catalog tools like get_product or search_products. The imperative framing makes the operation unmistakable.

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 explicit triggering conditions: before promising a delivery date, or when the human asks "will it arrive before X". That covers the main when-to-use case well. It stops short of naming an alternative or a when-not case, so it falls one step below the top score.

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