TF Handy Wash

Search the FAQ

search_faq

Read-onlyIdempotent

Published TF Handy Wash FAQ questions and answers in English or Spanish, with their source URLs. A query searches words in the questions and answers; without a query the first answers are returned.

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

Input Schema

Name	Required	Description
`limit`	No
`query`	No	Nonblank words to find in the published FAQ.
`language`	No

Output Schema

Name	Required	Description	Default
`url`	Yes
`total`	Yes
`notice`	Yes
`results`	Yes
`language`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 7, 2026

TDQS

A4.3/5.0

Behavior4/5

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

Annotations already declare read-only, idempotent, non-destructive, closed-world behavior, so the safety profile needs no restating. The description adds genuinely non-obvious traits beyond them: only published entries are returned, results span two languages, source URLs accompany answers, and a queryless call returns the leading answers rather than an error or empty set.

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

Conciseness5/5

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

Two sentences, both earning their place, with the content scope front-loaded and the query/no-query behavior following. No filler, no restatement of the title.

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?

An output schema exists, so return shape need not be spelled out, and the description still flags source URLs as part of results. For a zero-required-parameter lookup tool with all annotations present, the only loose end is the 'limit' semantics, which is small against the whole.

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 only 33%, with just 'query' documented, so the description needs to carry more weight than it does. It explains what query matches and that language is English or Spanish, but says nothing about 'limit' — no meaning, no default, no interaction with the queryless 'first answers' behavior. Partial compensation for a real gap.

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 and resource (search the FAQ questions and answers) plus scope qualifiers: published content only, English or Spanish, source URLs included. This clearly distinguishes it from every sibling, which fetch facility facts (hours, pricing, machines, amenities) rather than documentation content.

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?

Describes the two operating modes explicitly: a query matches words in questions and answers, and with no query the first answers are returned. That tells the agent when to pass a query versus call bare. It stops short of naming alternative tools, but no sibling overlaps this function, so the omission is minor.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All TF Handy Wash tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?