Skip to main content
Glama

Sofa guides

sofa_guide
Read-onlyIdempotent

Step-by-step guides: measure the room and the door, a sofa for a small flat, for dogs and cats, remove stains by cleaning code, assemble a modular sofa, a sofa for a holiday rental, reupholster or replace, and buying online. Returns steps, FAQs, accessory links and the guide URL.

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

Input Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, closed-world, so the safety profile is fully covered, but the description goes further by disclosing the response composition: steps, FAQs, accessory links, and the guide URL. That is meaningful context given there is no output schema. It stops short of describing behavior for uncovered questions or how multiple guides are chosen.

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?

Front-loaded with the 'Step-by-step guides:' label, followed by a scannable topic list and one sentence on return contents. The topic enumeration is long but each item adds retrieval value; there is minimal filler.

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 two-parameter lookup tool with no output schema, the description covers what it returns but leaves the input side thin (question phrasing expectations, language behaviour) and gives no routing guidance against four sibling tools. Adequate to invoke, but not complete enough to consistently select.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

With only 50% schema description coverage, the description needs to carry weight on parameters and does not: it never mentions the free-text 'question' field (documented in schema only as maxLength 300) nor the language switch. The useful notes about Spanish content, translation, and the default 'es' live entirely in the schema, not the description.

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 states a concrete resource (step-by-step guides) and enumerates the exact topics covered (measuring the room and door, small-flat sofas, pet-proofing, stain removal by cleaning code, modular assembly, holiday rentals, reupholstery, online buying), so an agent can match a user question to it. It does not explicitly contrast itself with the overlapping siblings (check_sofa_fits and sofa_bed_advice both cover fit/measurement territory), which keeps it 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 only: the topic list signals the kind of question that belongs here, and 'buying online' hints at a purchase-advice role. There is no explicit when-to-use or when-not clause and no named alternative (e.g. check_sofa_fits for a specific dimension check, answer_library for general questions), so the agent must infer routing.

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