Skip to main content
Glama

Find the right spare part

find_spare_part
Read-onlyIdempotent

Turns a part name or a symptom (e.g. «no desagua», «goma de la puerta», «resistencia del horno», «escobillas», «burlete nevera») into the part that usually fails, what to check before buying, difficulty, and an Amazon.es buy link (buy_url, affiliate) searched with the brand and model number so compatible parts show first.

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": {
      "question": "<question>"
    },
    "name": "find_spare_part"
  }
}

Input Schema

NameRequiredDescriptionDefault
brandNoBrand, e.g. Bosch, Balay, Siemens, Samsung, LG, AEG, Electrolux, Zanussi, Whirlpool, Indesit, Beko, Candy, Teka.
limitNoHow many parts (default 3).
languageNoLanguage of the answer (default: es). Content is in Spanish; translate it if needed.
questionYesThe part or the symptom in the user's words.
applianceNoAppliance: lavadora (washing machine), lavavajillas (dishwasher), secadora, frigorifico, horno, placa, campana, microondas. Free text is fine.
model_numberNoModel number / E-Nr. / PNC, if known.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already cover read-only, idempotent, open-world and non-destructive behavior, so the bar is lower, but the description adds real value beyond them: it discloses that buy_url is an affiliate link (monetization the agent should know about) and that the search is keyed on brand plus model number so compatible parts rank first. It does not state whether results are cached, rate-limited, or how reliable the compatibility match is.

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?

It is a single front-loaded sentence that leads with the core transformation and then enumerates the outputs. The parenthetical list of five Spanish symptom examples is slightly bulky but serves as concrete input guidance, so it mostly earns its 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?

With no output schema, the description carries the return-value burden and does so by naming the four result elements (likely-failing part, pre-purchase checks, difficulty, buy_url). What is missing is the ordering and shape of results across the limit parameter, and any caveat that compatibility is best-effort rather than guaranteed.

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%, so a 3 is the baseline; the description earns more by explaining the functional effect of brand and model_number — they are injected into the Amazon search so compatible parts appear first, which tells the agent why supplying them matters rather than just what they hold. Limit, language and appliance semantics remain schema-only.

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?

The description states a concrete transformation: a part name or symptom in, a diagnosed failing part plus pre-purchase checks, difficulty and an Amazon.es buy_url out. It also gives concrete symptom examples in Spanish («no desagua», «escobillas», «burlete nevera»), so an agent can recognize the input domain immediately and tell it apart from diagnose_error_code or repair_guide.

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 through the input framing ('turns a part name or a symptom'), and the 'what to check before buying' element hints at a pre-purchase context. There is no explicit when-to-use/when-not guidance and no routing to siblings such as find_model_number (for model lookup) or diagnose_error_code (for fault codes), leaving the agent to infer boundaries.

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