Skip to main content
Glama

Find sofas with real measurements

find_sofas
Read-onlyIdempotent

Sofas from Spanish shops (Conforama, Kenay Home, Banak, Klast Home, Balmi Home, fanmuebles) with width, depth, height, chaise depth, package sizes, fabric, removable covers, foam, price on the date checked, returns policy and the product url. Filter by type, maximum width/depth/price, removable cover, kids-and-pets friendly or shop. Prices and stock are those seen on the shop page on the date checked and can change.

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

Input Schema

NameRequiredDescriptionDefault
shopNo
textNoFree text, e.g. a model name.
typeNo2-3-plazas, chaise-longue, rinconera (corner), modular, sofa-cama (sofa bed) or relax (recliner).
limitNoDefault 5.
languageNoLanguage of the answer (default: es). Content is in Spanish; translate it if needed.
max_depthNoMaximum depth including chaise in cm.
max_priceNoMaximum price in EUR.
max_widthNoMaximum width in cm.
kids_and_petsNo
removable_coverNo

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, idempotentHint, openWorldHint and destructiveHint=false, so the safety profile is covered. The description adds genuinely useful context beyond that: the data source shops and the caveat that prices and stock reflect the shop page on the date checked and can change. It does not mention result ordering, pagination, or what happens when no match exists.

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?

Two sentences, front-loaded with the resource and source, then the filterable dimensions. The attribute list is dense and comma-heavy, but every item conveys what the result set contains, which is load-bearing given there is no output schema.

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

Completeness5/5

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

With 10 optional parameters and no output schema, the description carries the burden of describing the return shape, and it does so by enumerating the fields returned plus the freshness caveat. An agent has enough to call this correctly and know what to expect back.

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 70% and three params carry enums with their own descriptions, so the schema does much of the work. The description mirrors the filter set but adds no syntax or semantics for the undocumented remainder (text, limit, language), so it does not compensate for the coverage gap.

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 and resource ('find sofas') and pins the scope to sofas from named Spanish shops, then enumerates the attributes returned (width, depth, chaise depth, package sizes, fabric, price, returns policy, url). That is far more specific than the sibling advice tools (sofa_guide, choose_fabric, check_sofa_fits), though it never names a sibling explicitly to sharpen the boundary.

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?

The description implies usage by listing the filter dimensions (type, max width/depth/price, removable cover, kids-and-pets, shop), which tells an agent this is a filtered catalog lookup. It gives no explicit when-to-use vs when-not guidance and does not route the agent to check_sofa_fits or sofa_guide for the adjacent tasks.

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