Skip to main content
Glama

compatsy 3D printing

Check stock and price

check_stock
Read-onlyIdempotent

Availability and price per merchant, re-verified live when the data is over an hour old. Example: {"product_id":"e3d-v6-1-75mm-brass-nozzles-0-40mm-1-75mm","merchant_id":"e3d-online-com"}

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
merchant_idNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, open-world), so the bar is lower, and the description clears it by disclosing the caching/freshness policy: data older than an hour is re-verified live. That tells the agent to expect variable latency and guarantees current data, which is real behavioral value not present in structured fields.

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?

Two short sentences with the core capability first and the freshness caveat second; the example is compact and informative rather than padding. Slight cost: the example string is long and visually dominates the definition, but it earns its space by demonstrating ID format.

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 two-parameter read tool with no output schema and full annotation coverage, the definition supplies purpose, data-freshness behavior, and a concrete invocation example. Remaining gaps — response shape, currency, and behavior for an unknown product — are modest given the tool's simplicity and the absence of an output schema.

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 description coverage is 0%, so the description must carry parameter meaning, and it partially does: the example shows both parameters carrying slug-style identifiers, which conveys the expected ID format. However it never states that merchant_id is optional, what the format is when omitted, or that product_id is required — key facts left to the schema's required array alone.

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 resource and the exact payload: availability plus price, broken down per merchant. That is enough to separate it from get_product (product attributes) and search_products (discovery), though it never uses an explicit verb like 'check' or 'fetch' and doesn't state that it returns one row per merchant.

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 or when-not-to-use guidance, and no routing to siblings such as get_product or compare, which plausibly also surface pricing. The reader must infer usage entirely from the phrase 'availability and price per merchant'; nothing indicates whether merchant_id should be supplied for a single lookup or omitted for a multi-merchant comparison.

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.