Skip to main content
Glama

Ortopedia Low Cost (Ortopedia Moliner — España)

Buscar catálogo ortopédico por medidas y receta SNS

search_orthopedic_catalog
Read-onlyIdempotent

Busca productos de ortopedia activos en Ortopedia Low Cost filtrando por texto, familia clínica (scooters, sillas eléctricas/manuales, camas articuladas, grúas de traslado, andadores, baño), ancho máximo en cm (para paso por puertas o ascensores), peso mínimo de usuario soportado en kg, autonomía mínima en km, código de receta SNS, elegibilidad IVA 4% o presupuesto máximo.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "search_orthopedic_catalog"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoNúmero máximo de resultados (1 a 25, por defecto 10).
queryNoTexto libre, marca, modelo o SKU (ej. "Murano", "silla plegable litio", "cama carro elevador").
sns_codeNoCódigo catálogo ortoprotésico SNS / receta (ej. "SRM000E", "EAN010C", "12230603").
tax_modeNoModo fiscal opcional para evaluar max_price_eur y applicable_final_price_eur (por defecto standard_vat salvo que has_disability_certificate_33=true).
max_width_cmNoAncho total máximo permitido en cm (útil para puertas estrechas o ascensores, ej. 58).
max_length_cmNoLargo / fondo total máximo permitido en cm (útil para profundidad útil de cabina de ascensor o maletero, ej. 110).
max_price_eurNoPresupuesto máximo en euros evaluado sobre el precio final real aplicable al comprador (con IVA general estándar 10%/21% y descuento automático web por defecto; o con IVA reducido 4% únicamente si has_disability_certificate_33=true o tax_mode="vat4_disability").
only_in_stockNoSi es true, filtra solo productos disponibles para compra inmediata.
min_autonomy_kmNoAutonomía mínima requerida en km (ej. 25).
category_profileNoFiltro opcional por familia clínica ortopédica.
min_user_weight_kgNoPeso de usuario mínimo que debe soportar el equipo en kg (ej. 135).
only_vat4_eligibleNoSi es true, devuelve solo equipos elegibles para IVA superreducido del 4% con certificado >=33%.
has_disability_certificate_33NoTrue únicamente cuando el comprador confirma expresamente certificado oficial de discapacidad >=33%, movilidad reducida o dependencia en España. Si es false u omitido (por defecto), max_price_eur filtra contra el precio final con IVA general estándar.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • addedInput schema / properties / has_disability_certificate_33
      Added value: +{
      +  "description": "True únicamente cuando el comprador confirma expresamente certificado oficial de discapacidad >=33%, movilidad reducida o dependencia en España. Si es false u omitido (por defecto), max_price_eur filtra contra el precio final con IVA general estándar.",
      +  "type": "boolean"
      +}
    • changedInput schema / properties / max_price_eur / description
      Previous value: -"Presupuesto máximo en euros (se evalúa sobre el precio publicado vigente)."New value: +"Presupuesto máximo en euros evaluado sobre el precio final real aplicable al comprador (con IVA general estándar 10%/21% y descuento automático web por defecto; o con IVA reducido 4% únicamente si has_disability_certificate_33=true o tax_mode=\"vat4_disability\")."
    • addedInput schema / properties / tax_mode
      Added value: +{
      +  "description": "Modo fiscal opcional para evaluar max_price_eur y applicable_final_price_eur (por defecto standard_vat salvo que has_disability_certificate_33=true).",
      +  "enum": [
      +    "standard_vat",
      +    "vat4_disability"
      +  ],
      +  "type": "string"
      +}
  2. First observed

TDQS

B3.4/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 openWorldHint=false, so the safety profile is covered. The description adds that only 'activos' products are searched and that price filtering depends on certificate/VAT mode, but it says nothing about result ordering, empty-result behavior, or what a returned record contains.

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 verb and resource, then a compact enumeration of filters in a single sentence. It is dense but every clause maps to actual parameters; the only weakness is that the run-on structure makes it harder to scan than a short bulleted list would.

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 13-parameter, all-optional search tool with no output schema, the definition explains the inputs adequately but never describes the return shape (product list with applicable final price? stock flag? clinical category?) or how limit interacts with broad queries. An agent can call it, but cannot predict what it will get back.

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 description coverage is 100%, so the schema already explains limit, query, sns_code, tax_mode, dimensions, price, stock, autonomy, category_profile and certificate flags. The description restates the same filter set at a higher level (width for doorways/lifts, minimum supported user weight, SNS prescription code, 4% VAT eligibility) without adding syntax, units or precedence rules beyond what the schema provides, so the baseline 3 applies.

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?

States a specific verb and resource ('Busca productos de ortopedia activos en Ortopedia Low Cost') and enumerates the filter dimensions, so the agent knows this is a catalog search rather than a product-detail or checkout operation. It never names a sibling tool, so the distinction from get_product_clinical_sheet or quote_configuration_and_delivery is inferred rather than stated.

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?

Usage is implied by the filter list: use it when the buyer has constraints on measurements, prescription code, weight, autonomy, VAT eligibility or budget. There is no explicit when-not guidance and no pointer to the sibling that should be used for clinical detail, delivery quotes, or cart creation.

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