Skip to main content
Glama

Check availability

check_availability
Read-onlyIdempotent

Retrieves MSI salable quantity and lead-time details for up to 20 SKUs; pass needed quantities to see shortfalls or request per-warehouse stock breakdowns.

Instructions

MSI salable quantity (on-hand across the company's stock sources minus open reservations) for up to 20 SKUs, with a lead-time message. Pass qty_needed to see shortfalls. Set by_source to list per-warehouse quantities.

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
skusYes
by_sourceNo
qty_neededNoMap of SKU to quantity required

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.0

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds real context beyond that: the exact formula for salable quantity (on-hand minus open reservations), the 20-SKU ceiling, the presence of a lead-time message, and the shortfall behavior when qty_needed is supplied.

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?

Three short sentences, front-loaded with the metric definition, then the optional-parameter behaviors. No filler, no repetition of the title, and every clause carries distinct information.

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?

There is no output schema, yet the description still signals what comes back (quantities plus a lead-time message, per-source breakdown when requested, shortfalls when qty_needed is set). For a three-parameter read-only tool with a nested map parameter, that is nearly complete; only the exact response shape for the qty_needed case is left implicit.

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?

Schema coverage is only 33%, so the description must carry weight, and it does: by_source is explained as per-warehouse listing and qty_needed as a shortfall trigger, both adding behavioral meaning rather than restating types. The skus parameter's 'exactly as returned by search_parts' constraint lives only in the schema, which is fine, but no format hints for the qty_needed map appear in the description.

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?

States a specific resource and a precisely defined metric: 'MSI salable quantity (on-hand across the company's stock sources minus open reservations)'. The parenthetical definition of the computation and the 'up to 20 SKUs' scope make it unmistakably distinct from catalog siblings like get_product or search_parts.

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?

Gives conditional guidance for both optional parameters — 'Pass qty_needed to see shortfalls' and 'Set by_source to list per-warehouse quantities' — so the agent knows when to enable each. It does not, however, say when this tool should be chosen over a sibling such as get_product or get_customer_price, nor name any exclusion.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.