Skip to main content
Glama

Choose an upholstery fabric

choose_fabric
Read-onlyIdempotent

Which upholstery fabric suits a home with kids, dogs or cats (polyester, chenille, velvet, linen, microfibre, stain-resistant like Aquaclean, leather, faux leather, bouclé), how many Martindale rub cycles to ask for, what cleaning codes W/S/WS/X mean, and what foam density, springs and frame materials mean for comfort and durability.

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

Input Schema

NameRequiredDescriptionDefault
kidsNo
petsNo
languageNoLanguage of the answer (default: es). Content is in Spanish; translate it if needed.
questionNoThe question in the user's words, optional.
cat_scratchesNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.7/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, openWorldHint=false, so the safety profile is fully covered and the description does not contradict it. The description adds only content scope, with no information about response shape, length, or that answers are produced in Spanish by default. With annotations carrying the behavioral load, this is adequate but thin.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single run-on sentence of roughly 50 words with a long mid-sentence parenthetical fabric list. The subject list dominates and pushes the actual purpose to the end, so it is not front-loaded. The nine-item fabric enumeration in particular could be dropped or compressed without losing decision-relevant information.

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?

There is no output schema, so the description should explain what the agent gets back, and it does not (free text? recommendation list? length?). The default Spanish output and the question parameter are left entirely to the schema, and there is no sibling routing. For a five-parameter advisory tool at 40% schema coverage, the definition leaves real gaps.

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 only 40%, so the description should compensate. It partially does: 'a home with kids, dogs or cats' maps onto the kids, pets and cat_scratches booleans, but it says nothing about the question parameter or the language parameter (the latter only documented in the schema). The remaining content topics (Martindale, cleaning codes, foam density) are answer subjects, not parameters, so they add no meaning to the inputs.

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 is a topic inventory rather than a statement of function: it never says what the tool does (e.g. 'returns fabric recommendations'), only which subjects it covers. The enumerated subjects (Martindale rubs, cleaning codes W/S/WS/X, foam density, frame materials) do let an agent infer this is the fabric/material advice tool and distinguish it from check_sofa_fits or find_sofas. Purpose is inferable but not stated.

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 guidance at all: no statement of the trigger condition (user unsure about upholstery), no exclusions, and no routing to siblings such as sofa_guide or answer_library. The list of covered topics implicitly suggests a domain, but nothing tells the agent when to pick this tool over the alternatives.

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