Skip to main content
Glama

Plumbline - Contractor License Checks

Check a contractor's license record

check_contractor
Read-onlyIdempotent

Looks up a contractor's public credential in indexed state and local licensing records. Licenses, registrations and bond records mean different things. Each record carries a credential object (kind, label, note): kind is license, registration, business_license or bond when the source makes that clear; otherwise it is the generic "credential", and the note says what to verify with the issuing agency. The set of covered jurisdictions changes as sources are added, so this description does not list it. Inputs: a record number (license) or business name, with optional jurisdiction and exact listed city, or an entity_id from an earlier result, which selects that one record. Results: match (the credential record with its status and provenance); candidates (several records fit; each page holds up to 20 rows, total_candidates is the full count, offset pages through the rest, and entity_id selects one; a field with the same value on every row of a page is given once, in same_for_all_rows, and each row's entity block omits what the row already states); no_match_in_index (the index holds no record for that input, which does not mean the contractor is unlicensed; for a search across all jurisdictions, the message states how many covered jurisdictions were searched); or jurisdiction_not_covered (the requested jurisdiction is outside the index, with an official pointer URL where one is on file; the response message states exactly what the link is, or that none is on file, and for some jurisdictions the link is a consumer-protection or licensing-board page, not a license lookup). A name or city search sent with no jurisdiction that names a state outside the index ("Smith Plumbing Atlanta GA") answers candidates carrying not_covered (that state's not-covered answer, which also opens the message) when covered records fit the rest, and jurisdiction_not_covered when none do; those rows are records from other places. A name ending in a covered state's code that is also a word or short form ("Smith Plumbing Co", "Smith Plumbing LA") is not limited to that state; did_you_mean gives the name and jurisdiction to send for that state's search. A name whose full text matches nothing but whose last words name a city on the records ("Smith Plumbing Los Angeles") answers that name's records in that city, with city_read {city, name}; send the name alone for every city. Each record carries as_of_date: the publisher's own last-updated date where we have read one, else the day of our fetch. The freshness field on a match, and freshness_notes on candidates and on a no-match with a jurisdiction, state when a source's copy is behind its normal update schedule, slow to refresh by design, or still on its first full pass, with a plain note, the dates, and the issuing body's own lookup.

Input Schema

NameRequiredDescriptionDefault
cityNoOptional exact record-city filter, case-insensitive. Filters before pagination; does not represent service area or silently drop terms.
nameNoBusiness name, e.g. "Bayside Plumbing"
offsetNoPagination offset into the candidates list, a whole number, default 0. Each page holds up to 20 candidates; total_candidates in a candidates result is the full count. An offset past the end returns an empty candidates list with a message saying so; a negative or fractional offset returns an error.
licenseNoLicense number as printed on the license, truck, ad or contract, e.g. "1000002", "CCC 1332267", "MHIC 123872", "TECL40892"
entity_idNoThe exact entity.id from a previous response. It selects that one record, keeping records that share a number distinct, and overrides name and license. An id no record carries, or a jurisdiction or city that is not the record's own, returns an error that names the problem.
jurisdictionNoState or local jurisdiction: a state code ("CA" or "US-CA", any case), a full state name ("California", "District of Columbia"), or a local code such as "NYC". A state also covers the local jurisdictions inside it that the index holds (IL includes CHI, MD includes MD-HOWARD); each record states its own jurisdiction. Coverage spans dozens of US jurisdictions; a recognized place outside coverage returns jurisdiction_not_covered, and text that names no US state or local code returns an error listing the accepted forms.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / license / description
      Previous value: -"License number, e.g. \"1000002\""New value: +"License number as printed on the license, truck, ad or contract, e.g. \"1000002\", \"CCC 1332267\", \"MHIC 123872\", \"TECL40892\""
  2. Changed1 schema field changed
    • changedInput schema / properties / jurisdiction / description
      Previous value: -"State or local jurisdiction: a state code (\"CA\" or \"US-CA\", any case), a full state name (\"California\", \"District of Columbia\"), or a local code such as \"NYC\". Coverage spans dozens of US jurisdictions; a recognized place outside coverage returns jurisdiction_not_covered, and text that names no US state or local code returns an error listing the accepted forms."New value: +"State or local jurisdiction: a state code (\"CA\" or \"US-CA\", any case), a full state name (\"California\", \"District of Columbia\"), or a local code such as \"NYC\". A state also covers the local jurisdictions inside it that the index holds (IL includes CHI, MD includes MD-HOWARD); each record states its own jurisdiction. Coverage spans dozens of US jurisdictions; a recognized place outside coverage returns jurisdiction_not_covered, and text that names no US state or local code returns an error listing the accepted forms."
  3. Changed4 schema fields changed
    • addedInput schema / additionalProperties
      Added value: +false
    • changedInput schema / properties / entity_id / description
      Previous value: -"Select the exact entity.id from a previous response, preserving same-number record distinctions. Overrides name/license; supplied jurisdiction and city still constrain selection."New value: +"The exact entity.id from a previous response. It selects that one record, keeping records that share a number distinct, and overrides name and license. An id no record carries, or a jurisdiction or city that is not the record's own, returns an error that names the problem."
    • changedInput schema / properties / jurisdiction / description
      Previous value: -"State or local jurisdiction code, e.g. \"CA\" (\"US-CA\" style also accepted) or \"NYC\". Coverage spans dozens of US jurisdictions; GET /v1/coverage for the exact current list."New value: +"State or local jurisdiction: a state code (\"CA\" or \"US-CA\", any case), a full state name (\"California\", \"District of Columbia\"), or a local code such as \"NYC\". Coverage spans dozens of US jurisdictions; a recognized place outside coverage returns jurisdiction_not_covered, and text that names no US state or local code returns an error listing the accepted forms."
    • changedInput schema / properties / offset / description
      Previous value: -"Pagination offset into the candidates list, default 0. Use with total_candidates from a prior call to page through large candidate sets."New value: +"Pagination offset into the candidates list, a whole number, default 0. Each page holds up to 20 candidates; total_candidates in a candidates result is the full count. An offset past the end returns an empty candidates list with a message saying so; a negative or fractional offset returns an error."
  4. Changed2 schema fields changed
    • addedInput schema / properties / city
      Added value: +{
      +  "description": "Optional exact record-city filter, case-insensitive. Filters before pagination; does not represent service area or silently drop terms.",
      +  "type": "string"
      +}
    • addedInput schema / properties / entity_id
      Added value: +{
      +  "description": "Select the exact entity.id from a previous response, preserving same-number record distinctions. Overrides name/license; supplied jurisdiction and city still constrain selection.",
      +  "type": "string"
      +}
  5. First observed

TDQS

A4.2/5.0
Behavior5/5

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

Annotations cover the safety profile (readOnly, idempotent, non-destructive), so this is above the bar: the description discloses pagination behavior (20 rows per page, total_candidates, offset semantics), freshness and as_of_date provenance, coverage limits that change over time, and per-jurisdiction pointer URLs that may be consumer-protection pages rather than license lookups. That is substantial disclosure an agent cannot get from the annotations.

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

Conciseness3/5

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

Front-loaded with a good first sentence, but the body is roughly 350 words of tightly packed edge cases, including run-on sentences such as the one describing candidates carrying not_covered. The information is mostly load-bearing, yet it reads as a specification dump rather than a description an agent can scan quickly.

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?

There is no output schema, so the description carries the full burden of return-value semantics, and it does: it enumerates match, candidates (with pagination and same_for_all_rows collapsing), no_match_in_index, and jurisdiction_not_covered. Freshness signaling and the meaning of as_of_date are also covered, leaving little an agent would need to guess.

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 the baseline is 3, but the description adds relationship semantics the schema does not: license or name is the primary key with jurisdiction and city as optional filters, and entity_id overrides name and license to select a single record. It also explains the name/jurisdiction inference behaviors (did_you_mean, city_read) that no individual parameter description captures.

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?

Opens with a specific verb and resource: looks up a contractor's public credential in indexed state and local licensing records. It also defines what a 'credential' covers (license, registration, business_license, bond) versus a generic record. No siblings exist to distinguish from, so it loses nothing there, but the core statement is buried ahead of a long body of edge-case rules.

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 guidance on which input to send (record number, business name with optional jurisdiction/city, or an entity_id from an earlier result that selects one record) and explains the four outcome types and what each means, including the important caveat that no_match_in_index does not mean unlicensed. What it does not state is the top-level 'use this when' scenario for verifying a contractor before hiring, though that is largely implied.

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