Skip to main content
Glama

GATA Recambios: verified answers

answer_library
Read-onlyIdempotent

Searches GATA Recambios's library of reviewed answers and verified data (product specs, compatibilities, error codes, rules, measured comparisons, each with its primary source), plus the concrete products that solve the question (buy_url, affiliate). Returns the matching answers with their sources, or none when the library has no answer for the question. Content in Spanish.

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

Input Schema

NameRequiredDescriptionDefault
limitNoHow many answers to return (default 3).
questionYesThe user's question in their own words.

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 declare readOnly, idempotent, non-destructive, and closed-world behavior, so the safety profile is covered. The description adds genuinely new context: answers carry primary sources, the response may be empty, results include purchasable products with buy_url/affiliate links, and the content is Spanish-only. It does not describe ordering or relevance behavior, which keeps it short of a 5.

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

Conciseness5/5

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

Two sentences, front-loaded with the core action and resource, followed by the content inventory and the return/no-return behavior. No filler sentences, and the commercial (affiliate) disclosure is placed where it matters without bloating the text.

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 takes on responsibility for describing returns, and it does so at a useful level: matching answers with sources, plus concrete products with buy_url. The remaining gap is the shape of an individual answer record and how many products accompany a result, which an agent would need before parsing output confidently.

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%, with both `question` and `limit` (including the default of 3 and the 1–5 range) documented in the schema itself. The description adds no meaning beyond that — it does not explain how phrasing affects matches or whether Spanish input is required for the Spanish content — so the baseline of 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?

The description names a specific verb and resource — searching a library of reviewed answers and verified data — and enumerates what that library contains (product specs, compatibilities, error codes, rules, measured comparisons) along with the bundled product recommendations. This clearly separates it from siblings such as diagnose_error_code or find_spare_part, which target a single artifact rather than curated answers.

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 inventory of content the library covers, and the 'or none when the library has no answer' clause implies it is the lookup of last resort for verified content. However, there is no explicit when-to-use statement, no eligibility conditions, and no direct routing to the sibling tools for narrower tasks like error-code diagnosis or part lookup.

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