Skip to main content
Glama

compatsy home espresso

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":"lucca-puck-screen-58mm","merchant_id":"www-seattlecoffeegear-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.7/5.0
Behavior4/5

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

Annotations already establish read-only, idempotent, non-destructive, open-world behavior, so the bar is lower, and the description adds genuinely new behavioral context: results are re-verified live when cached data is over an hour old, which tells an agent about freshness and possible latency. It stops short of mentioning rate limits, auth requirements, or response shape.

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 compact sentences with the core result front-loaded and the freshness caveat immediately after. The inline example earns its space given zero schema descriptions, though the phrasing is telegraphic rather than fully explicit.

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-only lookup with no output schema, the description covers what is returned and freshness behavior. The remaining gap is the semantics of the optional merchant_id, which is the one thing an agent could get wrong when calling it.

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 0%, so the description must carry parameter meaning. The example conveys the ID formats (a product slug and a domain-style merchant slug), which is useful, but it never states that merchant_id is optional, what omitting it does, or how multiple merchants are represented.

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 data returned ('availability and price per merchant'), which pairs with the title 'Check stock and price' to make the verb unambiguous. It does not explicitly distinguish itself from siblings like get_product or compare, so an agent must infer the boundary.

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?

Usage is only implied: the phrase 'per merchant' plus the example hints that merchant_id filters the lookup, but nothing states when to choose this over get_product, search_products, or compare, nor what happens if merchant_id is omitted. No when-not guidance is given.

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.