Book It

Find a local provider

find_provider

Read-onlyIdempotent

Find home-service and trade businesses enrolled in Book It that serve a US ZIP code for a trade, such as HVAC, plumbing, roofing or lawn care. Returns each business's name, phone, website, the services that match the stated need, and its next open request window. Only businesses that enrolled and list that ZIP in their own service area appear; the result states the ordering rule, which is a fair daily rotation and never paid placement. An empty list means no enrolled business covers that trade and ZIP yet.

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": {
      "trade": "<trade>",
      "zip": "<zip>"
    },
    "name": "find_provider"
  }
}

Input Schema

Name	Required	Description
`zip`	Yes	The 5-digit US ZIP code where the work is.
`need`	No	What the person needs in a few words, such as "furnace blowing cold air". Used to surface matching services.
`trade`	Yes	The trade or a common name for it: "hvac", "furnace repair", "plumber", "roofer", "lawn care", "tree service".

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 21, 2026

TDQS

A3.9/5.0

Behavior4/5

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

Annotations already cover read-only, idempotent, non-destructive and closed-world, so the safety profile is known. The description still adds real value by disclosing the eligibility filter (only enrolled businesses that list that ZIP in their own service area), the ranking rule (fair daily rotation, never paid placement), and the empty-result meaning. It stops short of stating result limits or paging, but no such behavior is signalled.

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 sentences, front-loaded with purpose, then return fields, then the edge-case behavior. Every sentence carries information, and enumerating return fields earns its place because there is no output schema. Slight density could be trimmed, but nothing is redundant.

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 compensates by naming what comes back (name, phone, website, matching services, next request window). Parameters are fully covered by the schema and the ranking/empty-case behavior is disclosed. The only gap is the lack of guidance on what to do next in the sibling flow.

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 all three parameters are documented with formats, lengths and patterns in the schema itself. The description only restates that trade examples exist and that 'need' is used to surface matching services, which is marginal added meaning over the schema — baseline 3.

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 ('Find home-service and trade businesses enrolled in Book It') plus the scoping dimensions (US ZIP, trade) and example trades. It is clearly distinguishable from siblings like check_availability and quote_range, which handle different steps of the flow.

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 domain scoping ('serve a US ZIP code for a trade') implies this is the discovery step, and the empty-list semantics are explained. However, it never names an alternative or states when NOT to use it — with siblings like get_services and check_availability, an explicit routing hint (e.g. 'use check_availability for open windows') is missing.

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

All Book It 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?