Skip to main content
Glama

mireforma.net

Opciones para un concepto del presupuesto

reforma_budget_options
Read-onlyIdempotent

Catalogue options for one budget item (toilet, basin, tap, shower tray…), cheapest first, per brand.

Nivel 2 del embudo: opciones del catálogo para un concepto (inodoro, lavabo, grifo-lavabo, grifo-ducha, grifo-cocina, plato-ducha, electricidad, solado), de la más barata a la más cara, con la más barata de cada marca, tipo de precio, vigencia y enlace a la tarifa oficial. marca filtra.

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": {
      "concepto": "<concepto>"
    },
    "name": "reforma_budget_options"
  }
}

Input Schema

NameRequiredDescriptionDefault
marcaNoId de marca del catálogo, p. ej. roca
limiteNo
conceptoYesClave del concepto, p. ej. inodoro

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 readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so safety is covered. The description adds genuinely useful behavioral detail beyond that: results are sorted cheapest first, only the cheapest option per brand is returned, and each row carries price type, validity period and a link to the official tariff.

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 content is front-loaded and the opening English sentence carries the core facts, but the entire description is then restated in Spanish, so roughly half the text is duplication rather than new information. The underlying content is tight; the bilingual repetition is the only real bloat.

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?

With no output schema, the description carries the burden of describing returns, and it does so well (cheapest-per-brand, price type, validity, official tariff link). It falls short only on the `limite` parameter's effect on result count and on how an agent discovers valid concept keys and brand ids, which is left to trial or another tool.

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 67%; the description reinforces concepto with concrete key examples (inodoro, lavabo, grifo-lavabo…) and confirms that marca acts as a filter. The `limite` parameter is left unexplained in both schema and description, and the expected brand-id format is only implied by the schema example.

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 names a specific verb and resource ("Catalogue options for one budget item") and enumerates the concept keys it covers (toilet, basin, tap, shower tray, etc.), plus the ordering rule (cheapest first) and grouping (per brand). It does not explicitly contrast itself with siblings such as reforma_estimate_budget or reforma_search_catalog, so an agent must infer the boundary from the "Nivel 2 del embudo" framing.

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?

"Nivel 2 del embudo" implies this is a mid-step in a budgeting funnel and "marca filtra" signals that the marca argument narrows results, which gives implied usage context. However, there is no explicit statement of when to call this versus reforma_search_catalog or reforma_estimate_budget, and no when-not guidance.

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