LicenseGround

search_contractors

Discover active, verified trade contractors in California, Florida, or Texas by trade classification and location.

Args:
    state: Two-letter US state code ('CA', 'FL', or 'TX'). Required.
    trade: Trade category ('roofing', 'hvac', 'electrical', 'plumbing', 'general_contractor'). Required.
    city: Optional city to filter contractors by location.
    limit: Maximum number of contractors to return (1 to 50, default 10).

Returns:
    JSON list of verified contractors with active licenses, phone numbers, and addresses.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`city`	No
`limit`	No
`state`	Yes
`trade`	Yes

Output Schema

TableJSON Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedSep 30, 2026

TDQS

A3.9/5.0

Behavior3/5

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

With no annotations, the description carries the full burden. It discloses useful behavior: results are limited to CA/FL/TX, only active/verified licensed contractors are returned, and each record includes phone and address. However, it says nothing about authentication needs, rate limits, pagination beyond 'limit', sort order, or what happens when no results match.

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?

Front-loads the one-line purpose before the Args/Returns blocks, and every listed item carries information an agent needs. The Args/Returns formatting is slightly verbose against a schema that already carries the structure, but nothing is wasted.

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?

For a 4-parameter search tool with an output schema, the description covers the domain restrictions, required vs optional params, and value constraints. Return-value detail is partly redundant given the output schema, and edge cases (empty result set, pagination) are unaddressed, but nothing critical to calling it correctly is missing.

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 description coverage is 0%, so the description must compensate, and it largely does: it marks state and trade as required, enumerates the valid state codes and trade categories, documents city as an optional filter, and gives the limit range (1-50) and default (10). Minor gaps remain, e.g. case sensitivity or matching semantics for city, so not a full 5.

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 (Discover/search) plus resource (active, verified trade contractors), scoped to three named states and a non-empty domain of trades. This cleanly separates it from verification-oriented siblings like verify_license and check_federal_debarment, which check a single entity rather than discover a list.

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 by the framing ('Discover active, verified trade contractors'), but there is no explicit when-to-use or when-not-to-use guidance and no routing to alternatives such as verify_license for confirming a single contractor's status. Adequate but leaves the agent to infer the boundary with siblings.

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

All LicenseGround tools Inspect

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

Need Help?