Skip to main content
Glama

TexContractor

Find local home-service pros

find_local_pros
Read-onlyIdempotent

Find independent home-service pros (plumbers, AC/heating, electricians, handymen, roofers, mobile mechanics, cleaners, babysitters and more) listed on TexContractor in a US city. Returns names, service, city and a profile link where the homeowner can see work photos and text the pro directly. Free for homeowners, no lead fees for pros.

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": {
      "service": "<service>",
      "city": "<city>"
    },
    "name": "find_local_pros"
  }
}

Input Schema

NameRequiredDescriptionDefault
cityYesCity, e.g. 'Arlington'
limitNo
stateNoTwo-letter state code, e.g. 'TX'TX
serviceYesWhat the person needs, e.g. 'plumber', 'AC repair', 'garage door repair', 'handyman'

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description adds genuinely new behavioral context: results include a profile link where the homeowner can view work photos and text the pro directly, and that the service is free with no lead fees — useful for understanding the follow-up path. It stops short of describing result-count truncation or what happens on an empty search.

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 the core action and inventory, then the return contents, then marketplace terms. No redundancy. The closing 'Free for homeowners, no lead fees for pros' is marketing-adjacent rather than agent-critical, which keeps it from a perfect score.

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 steps in to summarize the returned fields and the downstream action (profile link, texting the pro), which is exactly what's needed. Minor gaps: the limit parameter's paging/truncation behavior is unexplained, and 'in a US city' sits slightly awkwardly against a state parameter defaulting to TX.

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 75%: city, state and service each carry descriptions and examples, so the schema does most of the work. The description reinforces the geographic scope ('in a US city') and gives implicit service vocabulary, but never mentions the limit parameter or its 1–10 cap, so it adds little meaning beyond the schema.

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?

The description names a specific verb and resource — finding independent home-service pros on TexContractor within a US city — and enumerates the covered trades (plumbers, electricians, roofers, cleaners, babysitters), so an agent knows exactly what domain this covers. It also states what comes back (names, service, city, profile link), which further pins the tool's identity apart from job-posting siblings.

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?

Usage is implied: a homeowner searching for a local service provider. There is no explicit statement of when to prefer this over list_open_job_requests or list_services, and no exclusions (e.g., what to do if no pros are listed). The context is clear enough to call correctly but the routing rules are left to inference.

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