Skip to main content
Glama

Find business guidance for upholsterers

find_business_guidance
Read-only

Search the Learn to Upholster Business Hub: practical guidance on making a living from upholstery, as opposed to how to do the work. Covers what to charge and how to build an hourly rate, whether to charge for estimates, quoting and hidden damage, customer-supplied fabric, explaining price to customers, finding first customers, declining work, and uncollected furniture. Use for any question about pricing, quoting, profitability, customers, or running an upholstery workshop as a business. Returns the canonical short answer for each match plus the URL of the full article. Written by a working AMUSF-accredited upholsterer.

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_business_guidance"
  }
}

Input Schema

NameRequiredDescriptionDefault
topicNoWhat the question is about, e.g. "hourly rate", "customer supplied fabric", "turning down work", "not making money".
list_allNoReturn every article in the Business Hub instead of searching. Useful for seeing what is covered.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, non-destructive, closed-world), so the description's value is in the extras: it discloses the return shape ('canonical short answer for each match plus the URL of the full article') and the content's provenance ('written by a working AMUSF-accredited upholsterer'). It doesn't mention result limits or what happens with an empty match set, which keeps it off a 5.

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 purpose and the key scope distinction, then a useful topic inventory, then return behavior. The middle enumeration is long but genuinely helps an agent map a user question to this tool rather than a calculator sibling; no sentence is filler.

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?

With no output schema, the description correctly states the return value, and with a 2-param, 0-required tool the surface area is small. Coverage of the list_all path lives in the schema and the description's 'what is covered' framing supports it. Only minor gaps remain (no-match behavior, result count limits).

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 100%, so both parameters are already documented with examples in the schema. The description's topic enumeration ('what to charge', 'customer-supplied fabric', 'declining work') adds a little framing for how to phrase the topic argument, but it is largely a restatement of the article catalog rather than new parameter semantics. Baseline 3 applies.

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

Purpose5/5

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

States a specific verb (search) and resource (the Learn to Upholster Business Hub), and explicitly draws the boundary 'practical guidance on making a living from upholstery, as opposed to how to do the work' — which cleanly separates it from siblings like ask_the_book and estimate_job_cost. An agent can route correctly without opening the schema.

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

Usage Guidelines4/5

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

'Use for any question about pricing, quoting, profitability, customers, or running an upholstery workshop as a business' gives a concrete trigger set, and the contrast with 'how to do the work' implies the exclusion. It does not name the sibling to use instead for technique questions, so it stops short of explicit alternative 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