Skip to main content
Glama
Sign In
Mostrador MCP

Mostrador MCP

by schbs
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Consultar stock

consultar_stock
Read-onlyIdempotent

Retrieves real-time stock levels for a product by its SKU. Use it to verify availability before quoting or selling; find the SKU first with the product search tool.

Instructions

Stock actual de un producto por SKU. Para precios con descuentos usá precio; para encontrar el SKU, buscar_producto.

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": {
      "sku": "<sku>"
    },
    "name": "consultar_stock"
  }
}

Input Schema

NameRequiredDescriptionDefault
skuYesSKU del producto, por ejemplo ET-HM-0001 (lo devuelve buscar_producto)

Output Schema

NameRequiredDescriptionDefault
skuYes
stockYes
nombreYes
unidadYes
disponibleYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.3/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so safety is covered structurally. The description adds only the dependency on buscar_producto for the SKU format, and says nothing about data freshness or what 'stock actual' represents (units vs. availability). Useful but thin 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?

Two short sentences with zero waste; the core purpose is front-loaded and the disambiguation clauses follow. Nothing could be cut without losing routing information.

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

Completeness5/5

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

For a one-parameter read with a full annotation set and an output schema, the description covers purpose, input origin and sibling routing. No return-value explanation is needed because the output schema supplies 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 100%: the single 'sku' parameter carries its pattern and an example (ET-HM-0001) plus its origin. The description only restates 'por SKU', so the schema does the heavy lifting and the baseline 3 applies.

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?

Names a specific verb+resource ('Stock actual de un producto por SKU') and immediately distinguishes itself from both siblings by naming them. An agent can tell exactly which tool retrieves stock versus price or SKU lookup.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives explicit routing rules: use 'precio' for discounted prices and 'buscar_producto' to obtain the SKU. Both alternatives and the conditions that select them are stated, leaving nothing to inference.

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

Deploy Server

Other Tools