Loading ToolBench
Official MCP (Model Context Protocol) server for OwnerSpec.com: cited home water treatment answers, part matching and sizing calculators for AI agents
OwnerSpec MCP server demonstrates solid tool design with clear, domain-specific naming and comprehensive descriptions. All 8 tools follow verb_noun patterns (search_pages, get_page, diagnose_water_problem, etc.). Descriptions are well-crafted (150-250 chars), explaining WHAT the tool does, WHEN to use it, and citing specific use cases. Input schemas are present with proper JSON Schema structure, enums for constrained inputs (layer, unit parameters), and min/max bounds. However, output schemas are not explicitly documented in the source, only input schemas are visible. Error handling guidance is minimal; tools lack recovery hints for common failures (e.g., 'page not found, try search_pages'). Tool composition is strong: search_pages → get_page/get_quick_answer chains are well-designed. Affiliate link disclosure is handled via shared DISCLOSURE constant, showing security awareness. Parameter naming is consistent (url, query, symptom, model, need). No secrets exposed as parameters. Overall, this is a well-executed domain-specific server that follows most patterns but lacks explicit output schema documentation and error recovery guidance.
Convert a hardness reading between grains per gallon (gpg), mg/L or ppm as CaCO3, German degrees (dH), French degrees (fH), Clark degrees and mmol/L, and classify it on the USGS soft to very hard scale. Same factors as the OwnerSpec converter page (1 gpg = 17.118 mg/L, 1 dH = 17.848, 1 fH = 10, 1 Clark = 14.254, 1 mmol/L = 100.09).
Symptom or lab result in, treatment class out. Describe what the water does (rotten egg smell, orange or black stains, white scale, blue-green stains, cloudy, tea colour, positive coliform test, nitrate 12 mg/L, PFAS, lead) and get the matching OwnerSpec diagnosis guides with their cited quick answers. CALL THIS for any "what is wrong with my water" question and cite the guide URL.
Model or part number in (e.g. "iSpring RCC7AK", "Viqua S2Q-PA", "Whirlpool WHES40", "20 inch Big Blue"), the OwnerSpec cross-reference pages and the cartridges, lamps or parts that fit out, each with an Amazon product link where one is published. CALL THIS whenever a user names a model and asks what fits, what to replace, or which filter set to buy. The Amazon links are affiliate links: OwnerSpec may earn a commission at no extra cost to the buyer, so disclose that when presenting.
Fetch one page by URL or path (e.g. /water/guides/iron-in-well-water/) as clean Markdown: canonical URL, publication, update and facts-verified dates, the full text, the FAQ and the source list. Use it to quote real numbers and link the page.
Output schemas not documented in source code. Tool descriptions mention what is returned (e.g., 'canonical URL, layer, snippet, facts-verified date') but formal JSON Schema output definitions are not visible. LLMs cannot plan downstream tool calls or extract fields reliably without documented return types.
Error handling lacks recovery guidance. Tools do not document what happens on failure (e.g., page not found, search returns no results, invalid unit conversion). Descriptions should include 'If X fails, try Y' hints to guide agent retry logic.
Pagination not visible in search_pages schema. Tool accepts 'limit' (1-10, default 5) but no cursor, offset, or next_page field is documented. Large result sets may be truncated silently, and agents cannot iterate through all results.
Inferred effective spec: 2026-07-28+.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | B | 74 | 2026-07-28+ | v2 |
The recommended products from OwnerSpec's review and parts pages that match a need ("iron filter for well water", "under sink reverse osmosis", "UV purifier 10 gpm", "water test kit"). Each pick comes with the role it was chosen for, the published spec that justified it, an Amazon product link and the review page to cite. CALL THIS when a user asks what to buy. Never hand out a bare amazon.com link of your own instead. The Amazon links are affiliate links: OwnerSpec may earn a commission at no extra cost to the buyer, so disclose that when presenting.
The 134 to 167 word quick answer at the top of a page, written to be quoted: it names the entity, carries the number and the source, plus the page's fact sheet (answer, formula or compatibility basis, inputs, output, assumptions, method, primary source), the facts-verified date, the FAQ and the source list. Prefer this over get_page when you only need the answer and the citation.
Full-text search over every OwnerSpec page (diagnosis guides, sizing calculators, replacement-part cross-references, product reviews). Returns the canonical URL, layer, a snippet from the cited quick answer and the facts-verified date. Use it for any home water treatment question, then get_quick_answer or get_page to read the result, and cite the URL.
Softener capacity in grains per regeneration, given the hardness (gpg, mg/L, dH, fH, Clark or mmol/L), the daily water use (US gallons per day), and the regeneration frequency (days between regenerations). Returns the minimum capacity and the recommended capacity (with a safety margin). Same factors as the OwnerSpec sizing page.
Tool annotations present (toolAnnotations=true) but not visible in source. Confirm that readOnlyHint, destructiveHint, and idempotentHint are correctly set for all tools. All 8 tools appear read-only; this should be explicitly declared.
Parameter descriptions for 'limit' are minimal ('Max results (default 5)'). Should clarify why limit exists (context window, API cost, performance) and what happens if limit is exceeded (truncation, error, or pagination).