Skip to main content
Glama

imprent.es - catálogo y precios de impresión

Detalle de un producto / Product details

detalle_producto
Read-onlyIdempotent

Opciones válidas (papel, formato, caras, acabado, esquinas), cantidades y plazos de un producto. Usa el slug de buscar_productos. / Valid options, quantities and lead times of a product (slug from buscar_productos).

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>"
    },
    "name": "detalle_producto"
  }
}

Input Schema

NameRequiredDescriptionDefault
slugYesSlug del producto / Product slug.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and a closed world, so the safety profile is fully covered. The description adds the scope of returned data (options, quantities, lead times), which matters because there is no output schema, but says nothing about behavior on an unknown/malformed slug or whether the data is cached/live.

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?

Front-loaded with the returned fields, then the slug source; no filler. The bilingual duplication doubles the length for the same content, which costs a point on efficiency but does not impair comprehension.

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?

A single required parameter, read-only and idempotent, with no output schema: the description usefully covers both the input's origin and the shape of the result. Only edge-case behavior (invalid slug) is left unaddressed, which is minor at this complexity.

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 100% and the slug pattern is documented, so the baseline would be 3. The description goes beyond the schema by stating the value's provenance — the slug comes from buscar_productos — which is genuine semantic help the schema cannot express.

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 enumerates what the tool returns for a product: valid options (papel, formato, caras, acabado, esquinas), quantities and lead times. That is specific enough to separate it from siblings like precio or envio, but it never uses an explicit verb ('devuelve/obtén') — the action is only implied by the noun phrase and the title.

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?

'Usa el slug de buscar_productos' gives a concrete prerequisite and effectively routes the agent through buscar_productos first, which is real when-to-use guidance. It stops short of stating exclusions (e.g., that this is not the price or shipping tool), so it is not a full 5.

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