Skip to main content
Glama

AIFEC

check_availability

Read-only

Whether a product (or one of its variants) can be bought in a given quantity right now, and what that quantity costs: unit_price and total (unit price × quantity, calculated by the shop). When the customer asks how much several units cost, call it with that qty and say its total: never multiply yourself.

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_availability"
  }
}

Input Schema

NameRequiredDescriptionDefault
qtyNo
product_idYes
session_idNoOnly if your client does not keep the MCP session (the Mcp-Session-Id header): the session_id that an earlier answer of this server gave you. It keeps the same cart between calls.
variant_idNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, so safety is covered; the description adds that the shop computes total = unit_price × qty and that answers are current ('right now'), which is useful beyond the annotations. However it never describes the availability result itself (boolean, error, or message), leaving the core response shape undisclosed.

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 sentences, purpose front-loaded, no filler. The only minor waste is the slight redundancy between 'calculated by the shop' and 'never multiply yourself', which restate the same guarantee twice.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no output schema, the description must carry return-value semantics; it names unit_price and total but not the availability indicator that the tool's name implies. Combined with the thin parameter coverage for product_id and variant_id, the definition is workable but leaves gaps an agent must discover by 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 only 25% (only session_id is documented), so the description carries more burden. It does explain qty semantics well, including that the server computes the total, and gestures at variant_id via 'one of its variants'. But product_id is unelaborated and variant_id's default of 0 (presumably 'no variant') is never explained.

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 states a specific verb and resource: whether a product or variant can be bought in a given quantity right now, plus the cost of that quantity. That clearly separates it from cart and catalog siblings in substance, but it never names an alternative (e.g. get_product or cart_add), so differentiation is implicit rather than explicit.

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 a concrete usage trigger: when the customer asks how much several units cost, call it with that qty and report the returned total. It also issues an explicit prohibition against multiplying manually, which is strong operational guidance. It stops short of saying when not to use it or which sibling handles adjacent needs.

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