Skip to main content
Glama

Buying a sofa online in Spain: your rights

buying_rights
Read-onlyIdempotent

14-day withdrawal for distance purchases, the exception for custom-made sofas (article 103.c), the 3-year legal warranty for new products, what to do if it arrives damaged, and each shop's returns policy, with official BOE sources.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "buying_rights"
  }
}

Input Schema

NameRequiredDescriptionDefault
shopNo
languageNoLanguage of the answer (default: es). Content is in Spanish; translate it if needed.
questionNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.9/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive and closed-world, so safety is covered. The description adds one genuinely useful behavioral fact beyond that - answers are grounded in official BOE sources - but says nothing about answer format, whether a shop-specific query returns only that shop's policy, or what happens with an empty question.

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 front-loaded sentence that leads with the most common concern (14-day withdrawal) and lists the rest compactly. A topic list is slightly dense to parse, but no sentence is wasted.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a zero-required-parameter knowledge tool with no output schema, the content scope is adequately covered. Still missing is any statement of what the agent gets back (prose answer? citations?) and how shop and question interact with the coverage listed.

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 coverage is 33%: the language parameter is self-documented and the enum speaks for itself, but shop and question carry no schema descriptions. The phrase "each shop's returns policy" hints that shop scopes the answer to one retailer, which is modest added meaning; the question parameter remains entirely unexplained in both schema and description.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description enumerates the specific legal topics covered (14-day withdrawal, article 103.c custom-sofa exception, 3-year warranty, damaged goods, per-shop returns), which makes the subject matter concrete. But it never states the operation - that the tool answers a consumer-rights question and returns sourced guidance - and it gives no signal distinguishing it from siblings like answer_library or sofa_guide.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no when-to-use or when-not-to-use guidance, and no alternative tool is named. The agent must infer on its own that rights/returns/legal questions belong here rather than in answer_library or sofa_guide.

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