Skip to main content
Glama
Sign In

contractors.fyi

by fyi.contractors
OverviewDiscussionsAdmin

Find ranked contractors

find_contractors
Read-onlyIdempotent

Contractors ranked by how many jobs of this kind their city permit record shows. Returns name, license where the state publishes one, job count, typical stated job value, the ZIP codes they work in most, and a profile URL. Ranking is by volume on the public record, not quality or reviews.

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": {
      "city": "<city>",
      "kind_of_work": "<kind_of_work>"
    },
    "name": "find_contractors"
  }
}

Input Schema

NameRequiredDescriptionDefault
cityYesCity id from list_coverage, e.g. los-angeles, new-york, austin
limitNoHow many to return, up to 25
kind_of_workYesKind of work, e.g. roofing, solar, adu, remodel

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / city / enum
      Previous value: -[
-  "los-angeles",
-  "san-francisco",
-  "seattle",
-  "new-york",
-  "austin",
-  "philadelphia",
-  "chicago",
-  "nashville",
-  "san-jose",
-  "sacramento",
-  "boulder",
-  "las-vegas",
-  "new-orleans",
-  "baton-rouge",
-  "raleigh",
-  "buffalo",
-  "cleveland",
-  "somerville",
-  "cambridge",
-  "minneapolis",
-  "bellevue",
-  "cary",
-  "elk-grove",
-  "anaheim",
-  "arlington-va",
-  "greensboro",
-  "naperville",
-  "everett",
-  "san-diego",
-  "chattanooga",
-  "orlando",
-  "tacoma",
-  "riverside",
-  "pittsburgh",
-  "miami-dade",
-  "marin-county",
-  "mesa",
-  "rockford",
-  "san-antonio",
-  "st-louis"
-]New value: +[
+  "los-angeles",
+  "san-francisco",
+  "seattle",
+  "new-york",
+  "austin",
+  "philadelphia",
+  "chicago",
+  "nashville",
+  "san-jose",
+  "sacramento",
+  "boulder",
+  "las-vegas",
+  "new-orleans",
+  "baton-rouge",
+  "raleigh",
+  "buffalo",
+  "cleveland",
+  "somerville",
+  "cambridge",
+  "minneapolis",
+  "bellevue",
+  "cary",
+  "elk-grove",
+  "anaheim",
+  "arlington-va",
+  "greensboro",
+  "naperville",
+  "everett",
+  "san-diego",
+  "chattanooga",
+  "orlando",
+  "tacoma",
+  "riverside",
+  "pittsburgh",
+  "miami-dade",
+  "marin-county",
+  "mesa",
+  "rockford",
+  "san-antonio",
+  "dekalb-county",
+  "denton",
+  "harris-county",
+  "st-louis",
+  "henrico-county"
+]
  2. Changed1 schema field changed
    • changedInput schema / properties / city / enum
      Previous value: -[
-  "los-angeles",
-  "san-francisco",
-  "seattle",
-  "new-york",
-  "austin",
-  "philadelphia",
-  "chicago",
-  "nashville",
-  "sacramento",
-  "boulder",
-  "las-vegas",
-  "new-orleans",
-  "baton-rouge",
-  "raleigh",
-  "buffalo",
-  "cleveland",
-  "somerville",
-  "cambridge",
-  "minneapolis",
-  "bellevue",
-  "cary",
-  "elk-grove",
-  "anaheim",
-  "arlington-va",
-  "greensboro",
-  "naperville",
-  "everett",
-  "chattanooga",
-  "orlando",
-  "tacoma",
-  "riverside",
-  "pittsburgh",
-  "miami-dade",
-  "marin-county",
-  "mesa",
-  "rockford",
-  "san-antonio"
-]New value: +[
+  "los-angeles",
+  "san-francisco",
+  "seattle",
+  "new-york",
+  "austin",
+  "philadelphia",
+  "chicago",
+  "nashville",
+  "san-jose",
+  "sacramento",
+  "boulder",
+  "las-vegas",
+  "new-orleans",
+  "baton-rouge",
+  "raleigh",
+  "buffalo",
+  "cleveland",
+  "somerville",
+  "cambridge",
+  "minneapolis",
+  "bellevue",
+  "cary",
+  "elk-grove",
+  "anaheim",
+  "arlington-va",
+  "greensboro",
+  "naperville",
+  "everett",
+  "san-diego",
+  "chattanooga",
+  "orlando",
+  "tacoma",
+  "riverside",
+  "pittsburgh",
+  "miami-dade",
+  "marin-county",
+  "mesa",
+  "rockford",
+  "san-antonio",
+  "st-louis"
+]
  3. Changed1 schema field changed
    • changedInput schema / properties / city / enum
      Previous value: -[
-  "los-angeles",
-  "san-francisco",
-  "seattle",
-  "new-york",
-  "austin",
-  "philadelphia",
-  "chicago",
-  "nashville",
-  "sacramento",
-  "boulder",
-  "las-vegas",
-  "new-orleans",
-  "baton-rouge",
-  "raleigh",
-  "buffalo",
-  "cleveland",
-  "somerville",
-  "cambridge",
-  "minneapolis",
-  "bellevue",
-  "cary",
-  "elk-grove",
-  "anaheim",
-  "arlington-va",
-  "greensboro",
-  "naperville",
-  "everett",
-  "chattanooga",
-  "orlando",
-  "tacoma",
-  "riverside",
-  "pittsburgh",
-  "miami-dade",
-  "marin-county",
-  "mesa",
-  "rockford"
-]New value: +[
+  "los-angeles",
+  "san-francisco",
+  "seattle",
+  "new-york",
+  "austin",
+  "philadelphia",
+  "chicago",
+  "nashville",
+  "sacramento",
+  "boulder",
+  "las-vegas",
+  "new-orleans",
+  "baton-rouge",
+  "raleigh",
+  "buffalo",
+  "cleveland",
+  "somerville",
+  "cambridge",
+  "minneapolis",
+  "bellevue",
+  "cary",
+  "elk-grove",
+  "anaheim",
+  "arlington-va",
+  "greensboro",
+  "naperville",
+  "everett",
+  "chattanooga",
+  "orlando",
+  "tacoma",
+  "riverside",
+  "pittsburgh",
+  "miami-dade",
+  "marin-county",
+  "mesa",
+  "rockford",
+  "san-antonio"
+]
  4. Changed1 schema field changed
    • changedInput schema / properties / city / enum
      Previous value: -[
-  "los-angeles",
-  "san-francisco",
-  "seattle",
-  "new-york",
-  "austin",
-  "philadelphia",
-  "chicago",
-  "nashville",
-  "sacramento",
-  "boulder",
-  "las-vegas",
-  "new-orleans",
-  "baton-rouge",
-  "raleigh",
-  "buffalo",
-  "cleveland",
-  "somerville",
-  "cambridge",
-  "minneapolis",
-  "bellevue",
-  "cary",
-  "elk-grove",
-  "anaheim",
-  "arlington-va",
-  "greensboro",
-  "naperville",
-  "everett",
-  "chattanooga",
-  "orlando",
-  "tacoma",
-  "riverside",
-  "pittsburgh",
-  "miami-dade",
-  "marin-county",
-  "mesa",
-  "rockford",
-  "san-antonio"
-]New value: +[
+  "los-angeles",
+  "san-francisco",
+  "seattle",
+  "new-york",
+  "austin",
+  "philadelphia",
+  "chicago",
+  "nashville",
+  "sacramento",
+  "boulder",
+  "las-vegas",
+  "new-orleans",
+  "baton-rouge",
+  "raleigh",
+  "buffalo",
+  "cleveland",
+  "somerville",
+  "cambridge",
+  "minneapolis",
+  "bellevue",
+  "cary",
+  "elk-grove",
+  "anaheim",
+  "arlington-va",
+  "greensboro",
+  "naperville",
+  "everett",
+  "chattanooga",
+  "orlando",
+  "tacoma",
+  "riverside",
+  "pittsburgh",
+  "miami-dade",
+  "marin-county",
+  "mesa",
+  "rockford"
+]
  5. Changed1 schema field changed
    • changedInput schema / properties / city / enum
      Previous value: -[
-  "los-angeles",
-  "san-francisco",
-  "seattle",
-  "new-york",
-  "austin",
-  "philadelphia",
-  "chicago",
-  "nashville",
-  "sacramento",
-  "boulder",
-  "las-vegas",
-  "new-orleans",
-  "baton-rouge",
-  "raleigh",
-  "buffalo",
-  "cleveland",
-  "somerville",
-  "cambridge",
-  "minneapolis",
-  "bellevue",
-  "cary",
-  "elk-grove",
-  "anaheim",
-  "arlington-va",
-  "greensboro",
-  "naperville",
-  "everett",
-  "chattanooga",
-  "orlando",
-  "tacoma",
-  "riverside",
-  "pittsburgh",
-  "miami-dade",
-  "marin-county",
-  "mesa",
-  "rockford"
-]New value: +[
+  "los-angeles",
+  "san-francisco",
+  "seattle",
+  "new-york",
+  "austin",
+  "philadelphia",
+  "chicago",
+  "nashville",
+  "sacramento",
+  "boulder",
+  "las-vegas",
+  "new-orleans",
+  "baton-rouge",
+  "raleigh",
+  "buffalo",
+  "cleveland",
+  "somerville",
+  "cambridge",
+  "minneapolis",
+  "bellevue",
+  "cary",
+  "elk-grove",
+  "anaheim",
+  "arlington-va",
+  "greensboro",
+  "naperville",
+  "everett",
+  "chattanooga",
+  "orlando",
+  "tacoma",
+  "riverside",
+  "pittsburgh",
+  "miami-dade",
+  "marin-county",
+  "mesa",
+  "rockford",
+  "san-antonio"
+]
  6. Changed1 schema field changed
    • changedInput schema / properties / city / enum
      Previous value: -[
-  "los-angeles",
-  "san-francisco",
-  "seattle",
-  "new-york",
-  "austin",
-  "philadelphia",
-  "chicago",
-  "nashville",
-  "sacramento",
-  "boulder",
-  "las-vegas",
-  "new-orleans",
-  "baton-rouge",
-  "raleigh",
-  "buffalo",
-  "cleveland",
-  "somerville",
-  "cambridge",
-  "minneapolis",
-  "bellevue",
-  "cary",
-  "elk-grove",
-  "anaheim",
-  "arlington-va",
-  "greensboro",
-  "naperville",
-  "everett",
-  "chattanooga",
-  "orlando",
-  "tacoma",
-  "riverside",
-  "pittsburgh",
-  "miami-dade"
-]New value: +[
+  "los-angeles",
+  "san-francisco",
+  "seattle",
+  "new-york",
+  "austin",
+  "philadelphia",
+  "chicago",
+  "nashville",
+  "sacramento",
+  "boulder",
+  "las-vegas",
+  "new-orleans",
+  "baton-rouge",
+  "raleigh",
+  "buffalo",
+  "cleveland",
+  "somerville",
+  "cambridge",
+  "minneapolis",
+  "bellevue",
+  "cary",
+  "elk-grove",
+  "anaheim",
+  "arlington-va",
+  "greensboro",
+  "naperville",
+  "everett",
+  "chattanooga",
+  "orlando",
+  "tacoma",
+  "riverside",
+  "pittsburgh",
+  "miami-dade",
+  "marin-county",
+  "mesa",
+  "rockford"
+]
  7. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare the safe read-only, idempotent, closed-world profile, so the bar is lower; the description adds real value by disclosing the ranking methodology and the data-coverage caveat that licenses appear only 'where the state publishes one.' It does not describe empty-result or pagination behavior, keeping it short of a 5.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two sentences, zero filler, ranking semantics front-loaded and the return-field inventory placed second where it is most useful. Every clause carries information an agent needs.

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, enumerating the returned fields (name, license, job count, typical value, ZIPs, profile URL) is exactly the right compensation, and the license-availability caveat prevents over-reading the data. It stops short of noting result limits or behavior when no contractors match.

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% and both enums plus the limit bounds are fully documented in the schema, so the baseline is 3. The description only loosely gestures at 'this kind' and 'city permit record' without adding format or selection guidance 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?

States a specific verb and resource ('Contractors ranked by how many jobs of this kind their city permit record shows') and pins down the ranking basis. This clearly distinguishes it from the raw-record sibling search_contractor_records, which the agent can infer without opening either schema.

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 description implies the use case (find contractors for a given city and kind of work) and warns that ranking is by volume 'not quality or reviews,' but never says when to prefer this over search_contractor_records or check_solar_quote/permitting siblings. Usage is inferable rather than stated.

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

All contractors.fyi toolsInspect
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