Skip to main content
Glama

Ask The Working Upholsterer’s Bible

ask_the_book
Read-only

Ask a practical upholstery question and get an answer grounded strictly in the text of The Working Upholsterer’s Bible by Shaun Greenwood (master upholsterer, AMUSF accredited) — traditional and modern techniques, materials, UK fire regulations, projects and pricing. Answers cite the source chapter URL on learntoupholster.com.

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

Input Schema

NameRequiredDescriptionDefault
questionYesThe upholstery question, in plain English (max 300 characters).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already establish readOnly, non-destructive, closed-world behavior, so the safety profile is covered. The description adds genuine behavioral value beyond them: answers are constrained to a single named source rather than general knowledge, and responses are sourced with a chapter URL on learntoupholster.com. It does not say how off-topic or unanswerable questions are handled, which is the main residual unknown.

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 action and resource, then scope, then output behavior — a sensible ordering in a single sentence. The parenthetical credential '(master upholsterer, AMUSF accredited)' is partly marketing padding, though it does signal answer authority, so it is not purely waste.

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?

For a single-parameter retrieval tool with no output schema, the description covers what goes in, what comes back, and how answers are sourced. What is missing is edge-case behavior — refusal of non-upholstery questions, answer length, or how conflicts between book content and current UK regulations are handled — which matters given the fire-regulation topic.

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?

There is one parameter with 100% schema description coverage, so the schema already documents the question string and its 300-character limit. The description only echoes that the question should be practical upholstery content, adding marginal meaning. Baseline 3 applies when the schema does the heavy lifting.

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?

A specific verb and resource: ask an upholstery question, get an answer grounded strictly in the named book, with the topical scope (techniques, materials, UK fire regulations, pricing) enumerated. That is far more than a restated title. The one gap is that the enumerated topics overlap with siblings such as check_fire_regulations and estimate_job_cost, and the description never states that this tool returns textual answers from the book rather than computed results.

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 phrase 'ask a practical upholstery question' implies the intended context, and the topic list sketches the domain. However there is no explicit when-not guidance and no routing statement toward the calculator or regulation-checking siblings, even though the description's own topic list invites overlap with them. Usage is implied, not directed.

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