Skip to main content
Glama

colegios.shop — uniformes escolares

Talle sugerido por edad

talle_sugerido
Read-onlyIdempotent

Sugiere un talle por edad (y opcionalmente para una prenda). Es una sugerencia, nunca una certeza: que lo confirme con la tabla de medidas. Si la tienda tiene el ayudante apagado, lo dice.

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": {
      "slug": "<slug>",
      "edad": "<edad>"
    },
    "name": "talle_sugerido"
  }
}

Input Schema

NameRequiredDescriptionDefault
edadYesEdad del chico en años (opcional). Sólo sirve para sugerir el talle si la tienda tiene prendido el ayudante de talle.
slugYesIdentificador de la tienda (lo que va después de colegios.shop/t/).
prendaNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already mark this as read-only, idempotent, non-destructive, and closed-world. The description adds useful behavioral context by warning that the answer is a suggestion, not a certainty, and by stating that it reports when the store has the size helper turned off.

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 three short sentences with no waste. Purpose, caveat, and disabled-helper behavior are front-loaded and easy to scan.

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?

For a low-complexity read-only suggestion tool with annotations and no output schema, the description covers the key caveat and the disabled-helper case. It could say more about the response or about slug, but nothing critical for invoking it correctly is missing.

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 67%, and the description clarifies that age drives the suggestion and that garment is optional. It does not mention the required slug parameter, so it only partially adds meaning beyond the schema.

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: suggests a size by age, optionally for a garment. It is understandable without opening the schema, but it does not explicitly distinguish itself from siblings such as buscar_productos or ver_producto.

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?

It gives implied usage context by saying the result is only a suggestion and should be confirmed with the size chart. However, it does not state when to use this tool instead of sibling tools or any exclusions beyond the store having the helper disabled.

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