Skip to main content
Glama

check_license

Look up one roofing contractor license or registration by state and number. Returns status as published by the state regulator, a machine-readable verdict, licensee name, city, expiration, and provenance (regulator source URL + fetch date). Verdicts: licensed-active | licensed-not-active (trade license states like FL), registered-active | registered-not-active (registration states like NJ/PA — business registration, not a trade license), not-in-roster, not-found. The verdict is derived from the regulator-published status, not a recommendation. Use this when a user asks "is this roofing contractor licensed" or has a license number from a truck, yard sign, ad, or contract.

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": {
      "state": "<state>",
      "license_number": "<license_number>"
    },
    "name": "check_license"
  }
}

Input Schema

NameRequiredDescriptionDefault
stateYesTwo-letter state code or state name, e.g. FL, tx, Florida
license_numberYesLicense number as printed, e.g. CCC1325838 or CGC061405; hyphens/spaces are ignored

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior5/5

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

With no annotations, the description carries the full burden and does so well: it describes returned fields, enumerates machine-readable verdict meanings, notes that active registration is business registration rather than a trade license, and clarifies that the verdict is regulator-derived, not a recommendation. That is unusually strong behavioral context for a lookup tool.

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?

The first sentence establishes the purpose, then return values, verdict taxonomy, caveat, and usage trigger follow in a logical order. It is dense but every sentence contributes useful information.

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?

Because there is no output schema, the description must explain what comes back, and it does: status, verdict, licensee name, city, expiration, and provenance. Combined with the 100%-covered input schema, an agent has enough to call this correctly.

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 the schema already documents state format and license-number formatting. The description adds only the high-level 'by state and number' framing, which matches the schema rather than extending it.

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: look up one roofing contractor license or registration by state and number. The singular lookup scope and mention of a specific license number clearly distinguish it from a broader sibling such as search_licensees.

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?

Explicitly says to use this when the user asks whether a contractor is licensed or provides a license number from a truck, sign, ad, or contract. It does not name when-not-to-use cases or direct agents to alternatives, so it falls just short of full routing guidance.

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