Skip to main content
Glama

GATA Domótica: verified answers

answer_library
Read-onlyIdempotent

Searches GATA Domótica'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

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, closed-world and non-destructive, so the safety profile is covered. The description adds genuinely non-structured context: that every answer carries a primary source, that results include commercially linked products (buy_url, affiliate), that an empty result set is a legitimate outcome, and that content is Spanish-only. Pagination and ranking order are unmentioned, but that is minor given the empty-result and sourcing disclosures.

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 dense sentence followed by a return-behavior sentence, with the core verb and resource front-loaded and no filler. The parenthetical inventory is long enough to be slightly run-on but each item (source, buy_url, affiliate) carries real selection value.

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?

There is no output schema, so the description correctly takes on return-value explanation: matching answers with sources, plus products, or an empty result. Combined with the Spanish-language constraint and the verified-data scope, an agent has enough to call it and interpret the response, with only ordering and matching-precision left unstated.

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 both parameters are already documented (question as the user's own words, limit 1-5 default 3), which puts this at the baseline. The description adds only the indirect hint that questions should be Spanish ('Content in Spanish'), with no extra guidance on phrasing, scoping, or how limit interacts with result quality.

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 pairs a specific verb ('Searches') with a well-characterized resource: a library of reviewed answers and verified data covering specs, compatibilities, error codes, rules and measured comparisons. It also discloses a secondary output (concrete products with buy_url/affiliate), so an agent knows this is both a Q&A lookup and a product resolver. It does not name a sibling such as check_compatibility or recommend_smart_home_products, which keeps it just short of a 5.

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 rather than stated: use it when a question might already have a reviewed answer, and the fallback behavior ('returns none when the library has no answer') signals when to move on. There is no explicit 'use X instead when...' routing against check_compatibility or recommend_smart_home_products, so the agent must infer the boundary.

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