Skip to main content
Glama

GATA Sofás: verified answers

answer_library
Read-onlyIdempotent

Searches GATA Sofás'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.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, openWorldHint=false, idempotentHint and destructiveHint=false, so the safety profile is covered. The description usefully adds that answers carry primary sources, that an empty result is possible when the library has no answer, and that output includes affiliate/buy_url product recommendations, plus the Spanish-language constraint. It does not cover result ordering, source trust tiers, or what a partial match looks like.

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?

A single dense sentence that front-loads the search action and packs the content scope, source provenance, product results and the empty-result case. It is information-rich rather than padded, though the parenthetical enumeration makes it slightly hard to scan.

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: matching answers with sources, the none-result case, and product objects with buy_url/affiliate. Combined with the Spanish-language note and read-only annotations, nothing essential for correct invocation is missing beyond retrieval ranking details.

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 baseline is 3; the description adds some meaning by framing the query as a natural-language question about the catalog's subject matter, and implies limit-truncation by saying it returns 'the matching answers.' It does not explain what limit does when fewer answers match, but the schema handles both parameters adequately.

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 specific verb ('Searches') and resource ('library of reviewed answers and verified data'), enumerates the content types (specs, compatibilities, error codes, rules, comparisons) and notes it also returns solving products. It implicitly differentiates from task-specific siblings like check_sofa_fits or choose_fabric, though it never names an alternative explicitly.

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: the open-ended phrasing and 'question in their own words' suggest free-form questions rather than the specific calculators/guides siblings. There is no explicit when-to-use or when-not-to-use statement, and no routing to find_sofas or sofa_guide for browsing intent.

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