Skip to main content
Glama

The Builders Supply catalog

Check availability

check_availability
Read-onlyIdempotent

Availability of one or more SKUs with the meaning of each state: in stock with a real count, available with unknown quantity, ordered from the supplier with a lead time, made to order, assembled to order, out of stock, not for sale.

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": {
      "skus": "<skus>"
    },
    "name": "check_availability"
  }
}

Input Schema

NameRequiredDescriptionDefault
skusYesone to 10 store SKUs
quantityNoquantity wanted, checked against order multiples and the published count

Output Schema

NameRequiredDescriptionDefault

No arguments

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?

The annotations already declare readOnlyHint, idempotentHint, openWorldHint=false, and destructiveHint=false, so the safety profile is clear. The description adds meaningful behavioral context by explaining each availability state, including lead times for supplier-ordered items and distinctions like made to order versus assembled to order.

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?

The description is a single front-loaded sentence that communicates the core purpose before enumerating availability states. It is information-dense without unnecessary preamble, though the long enumeration makes it slightly less scannable than it could be.

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?

The tool has only two parameters, full schema coverage, an output schema, and clear annotations, so most structural details are already covered. The description supplies the missing semantic context: what each availability state means, which is essential for interpreting results correctly.

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 100%, so the input schema already documents both the skus and quantity parameters in detail. The description reinforces that multiple SKUs can be checked, but it adds little parameter-level meaning beyond what the schema provides.

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 clearly states that the tool checks availability for one or more SKUs, and it enumerates the possible availability states. This distinguishes it from sibling tools like get_product or search_products, which focus on product details and discovery rather than availability status.

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 description implies the tool is used when an agent needs to verify whether SKUs are purchasable or when they will be available. However, it does not explicitly say when to use this tool versus alternatives such as get_product or compare_products, nor does it state any exclusions.

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