Skip to main content
Glama

mireforma.net

Buscar distribuidores e instaladores

reforma_search_directory
Read-onlyIdempotent

Find distributors, installers and shops by category, brand and area in Spain. No phones or emails.

Busca empresas del directorio (distribuidores, instaladores, tiendas) por categoría de la taxonomía, marca y zona. categoria es un id de familia (fontaneria, banos…). ine es el municipio, provincia el código de dos dígitos, ccaa la comunidad. Ordena por cercanía administrativa: mismo municipio, luego provincia, luego comunidad. No devuelve teléfonos ni correos.

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_directory"
  }
}

Input Schema

NameRequiredDescriptionDefault
ineNoCódigo de municipio INE, 5 dígitos
ccaaNoComunidad: CT, AN, o un nombre como Catalunya
marcaNoId, slug o external_id de la marca
categoriaNoId de familia o categoría mireforma, p. ej. fontaneria
provinciaNoCódigo de provincia INE, 2 dígitos

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior4/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. The description adds genuinely useful behavior beyond that: results are ranked by administrative proximity (same municipality, then province, then community) and phones/emails are deliberately excluded from results — stated twice, in both languages.

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?

Front-loaded and readable, but the entire content is duplicated in English and Spanish, roughly doubling length without adding information for an agent. The Spanish half does carry slightly more detail (ranking order), so the duplication is not purely wasted, but it is inefficient.

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 read-only, all-optional-filter search with no output schema, the description covers the entity domain, the filter vocabulary, result ordering and the notable absence of contact details. It omits pagination/result-count behavior and how multiple filters interact, which are the remaining gaps.

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 baseline is 3. The description restates what the schema already says (categoria as a family id, ine as municipality, provincia as a two-digit code, ccaa as the community) and adds little new syntax or format detail, nor does it say whether filters combine as AND or OR.

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 concrete verb and resource: find distributors, installers and shops in a business directory, filtered by category, brand and area in Spain. The domain and entity types are unambiguous, though it never names a sibling (e.g. reforma_search_catalog) to contrast against, so routing 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 only implied: it is a directory lookup, so an agent can infer it is for locating businesses rather than products or budgets. There is no explicit when-to-use/when-not-to-use guidance and no mention of when to prefer the catalog or municipality siblings.

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