Skip to main content
Glama

renovation-room

Search Renovation Pros

search_pros
Read-only

Search The Renovation Room's directory of Chicagoland member contractors by trade, service, or company name. Coverage is Chicago, its suburbs, Northwest Indiana, and Southern Wisconsin only. Returns published member businesses with their trades, service areas, and profile links; use each result's id with get_pro for details.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
queryYesPass ONLY the trade, service, or company name (e.g. "roofing", "fence installation", "Grindstone Roofing") — not a sentence and not a location. 2-80 characters.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / query / description
      Previous value: -"Trade, service, or company name to search for. 2-80 characters."New value: +"Pass ONLY the trade, service, or company name (e.g. \"roofing\", \"fence installation\", \"Grindstone Roofing\") — not a sentence and not a location. 2-80 characters."
  2. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already establish this is a safe read-only, closed-world operation. The description adds genuinely useful behavior beyond that: the fixed geographic coverage boundary and the fact that only published members are returned, which tells the agent what results will and won't appear.

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?

Three tight sentences that front-load the purpose, then coverage limits, then return shape and the get_pro handoff. No filler, though the geographic scope and return details could be marginally tightened.

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?

With no output schema, the description compensates by describing the return contents (published members with trades, service areas, profile links) and how to continue (id with get_pro). For a single-param search tool this covers everything an agent needs to call it correctly.

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 100%, so the query parameter's constraints (single trade/service/name, 2-80 chars, no sentence, no location) are already fully documented in the schema. The description adds minimal parameter-level meaning beyond naming the searchable dimensions.

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 (Chicagoland member contractor directory) and names the qualifying dimensions (trade, service, company name). It is clearly distinguishable from get_pro, which it explicitly points to for details.

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?

Gives clear context for when to use it and names get_pro as the follow-up for result details via the id. It does not state exclusions (e.g., non-member or out-of-region searching), so it falls just short of full when/when-not guidance.

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