Skip to main content
Glama

mireforma.net

Buscar tarifas de fabricantes

reforma_search_catalog
Read-onlyIdempotent

Search official manufacturer price lists (list price, EUR excl. VAT) by brand, family, reference, text or price range.

Busca referencias del catálogo de tarifas oficiales de fabricantes (PVP recomendado o tarifa, en euros y sin IVA). Filtra por marca, familia de la reforma (griferia, electricidad, climatizacion…), referencia exacta, texto libre y rango de precio. Devuelve el enlace al PDF original del fabricante (url_origen); mireforma.net no republica esos PDF ni incluye teléfonos o correos. No es un presupuesto.

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

Input Schema

NameRequiredDescriptionDefault
qNoTexto libre sobre nombre, referencia o serie
refNoReferencia exacta del fabricante
marcaNoId o nombre de la marca, p. ej. roca o Legrand
familiaNoFamilia de la reforma, p. ej. griferia, electricidad, banos
precio_maxNoPrecio máximo sin IVA, en euros
precio_minNoPrecio mínimo sin IVA, en euros

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already cover safety (readOnly, idempotent, non-destructive, closed-world), so the description's added value is in what comes back: a link to the manufacturer's original PDF (url_origen) and the fact that PDFs, phone numbers and emails are not republished. That is genuinely useful behavioral context. It stops short of describing result limits, pagination or whether an empty result is possible.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The English lead sentence is well front-loaded, but the Spanish paragraph is a near-complete restatement of the same content rather than a translation of anything extra. Bilingual duplication roughly doubles the token cost for an agent that only needs one pass, though the 'no republica PDFs' and 'No es un presupuesto' clauses earn their place.

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 an all-optional, read-only search tool with no output schema, the definition covers intent, filter axes, provenance of results and the key negative framing. The main residual gap is result-shape/paging behavior, which nothing else in the structured data supplies.

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 all six parameters are already documented in the schema, including the excl.-VAT/eur semantics. The description restates the same filter set ('marca, familia..., referencia exacta, texto libre y rango de precio') without adding format hints such as whether marca accepts an id, a name, or both. 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?

Specific verb+resource ('Search official manufacturer price lists') with an explicit scope ('list price, EUR excl. VAT') and the fields it searches. It also pre-empts confusion with a named adjacent concept: 'No es un presupuesto', which separates it from reforma_estimate_budget / reforma_budget_options. An agent can route to it without opening the schema.

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?

Clear about the available retrieval axes (brand, family, exact reference, free text, price range) and about the negative case (it is not a budget/estimate). It does not, however, say when to prefer it over a sibling such as reforma_search_directory or reforma_budget_options by name; the steering is implicit.

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