Skip to main content
Glama

get_product_availability

Read-only

Consulta disponibilidad actual sin cantidades ni garantía de corte.

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": "get_product_availability"
  }
}

Input Schema

NameRequiredDescriptionDefault
product_idYes
combination_idNo

Output Schema

NameRequiredDescriptionDefault

No arguments

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?

The annotations already declare this as a read-only, closed-world operation, and the description adds valuable behavioral context by warning that results do not include quantities or a guaranteed stock cutoff. It does not describe error handling or rate limits, but for a simple read tool this is a useful disclosure beyond the annotations.

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?

The description is a single, front-loaded sentence with no unnecessary words. It efficiently communicates the core purpose and the key output limitation.

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?

For a low-complexity read tool with an output schema and read-only annotations, the description covers the main purpose and output caveat. However, it is incomplete regarding parameter usage—especially what combination_id represents—which is important given the zero schema description coverage.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/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 the burden of explaining product_id and combination_id. It does not mention either parameter or clarify that combination_id is optional and likely used for variants, leaving the agent with only the raw property names.

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 clear verb and resource: querying current availability for a product. It adds useful scope by noting the absence of quantities and stock guarantees, but does not explicitly distinguish itself from siblings like get_product or search_products.

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 phrase 'disponibilidad actual' implies the tool should be used to check whether a product is available now. However, there is no explicit guidance on when to choose this over get_product or search_products, nor any stated prerequisites or exclusions beyond the lack of quantities and guarantees.

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