Skip to main content
Glama

Find a contractor

find_contractor
Read-onlyIdempotent

Check whether PaisaLocal builds this type of outdoor project at this ZIP code (Dallas-Fort Worth only). project_type: retaining-wall, outdoor-kitchen, concrete (patio/driveway), curb-stone (edging) or french-drain.

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": {
      "zip": "<zip>",
      "project_type": "<project_type>"
    },
    "name": "find_contractor"
  }
}

Input Schema

NameRequiredDescriptionDefault
zipYes5-digit US ZIP code of the job
project_typeYesretaining-wall | outdoor-kitchen | concrete | curb-stone | french-drain

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive, and openWorldHint=false, so the read-only surface is covered. The description adds the closed service-area constraint, which is real context beyond annotations. It says nothing about what actually comes back (a boolean eligibility answer, a list of contractors, or an error for an unsupported area), which matters since there is no output schema.

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?

Two sentences, front-loaded with the core check and then the service-area caveat and value glossary. The project_type list partly repeats the schema, but the parenthetical glosses justify it. No filler.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple two-required-parameter read tool the description is nearly sufficient, and annotations carry the safety profile. The notable gap is outcome shape: there is no output schema, and the description never says what an eligible vs. ineligible response looks like or how out-of-area ZIPs are handled.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/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, giving a baseline of 3. The description earns extra credit by expanding ambiguous project_type tokens — "concrete (patio/driveway)" and "curb-stone (edging)" — which helps an agent map a user's phrasing onto the right value even without a schema enum.

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

Purpose4/5

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

"Check whether PaisaLocal builds this type of outdoor project at this ZIP code" gives a concrete verb (check availability), a resource (build capability for a project type), and scope (ZIP level). The parenthetical "Dallas-Fort Worth only" further narrows it. It does not explicitly distinguish itself from get_estimate or request_site_visit, so it stops short of a 5.

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 DFW-only restriction functions as an implicit "when not to use" for out-of-area ZIPs, which is genuinely useful for tool selection. However, it never states the relationship to the sibling flow (e.g., call this before get_estimate or request_site_visit) or what to do if the answer is negative.

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