Skip to main content
Glama

search_licensees

Search roofing contractors by name, firm, or partial license number, optionally within a state and city. Returns up to 50 regulator-sourced records with a true total count. Use this when the user has a name but no license number.

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": {
      "query": "<query>"
    },
    "name": "search_licensees"
  }
}

Input Schema

NameRequiredDescriptionDefault
cityNo
limitNo
queryYesName, firm, or license fragment
stateNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full behavioral burden. It does disclose useful traits beyond the schema: results are regulator-sourced, capped at 50, and accompanied by a true total count. It says nothing about auth requirements, rate limits, pagination, or how fuzzy the partial matching is, leaving real gaps for a tool whose output is the whole point.

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?

Three short sentences, zero filler, with the core capability front-loaded and the routing condition placed last where it is most useful for a selection decision.

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?

There is no output schema, so the description correctly covers the return shape (up to 50 records, true total count, regulator-sourced). Parameters are mostly accounted for and the routing condition is present. Missing pagination and filter-format details keep it from being fully complete.

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 only 25% (just `query`), so the description must compensate. It does explain `query` (name, firm, or license fragment) and gestures at `state`/`city` as optional geographic narrowing, and "up to 50" clarifies the `limit` ceiling. However, it omits the default limit of 10 and gives no format guidance for state/city (abbreviation vs full name), so the compensation is partial.

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 ("Search roofing contractors") plus the accepted match keys (name, firm, partial license number) and an optional geographic scope. The closing line implicitly separates it from the license-number-oriented siblings such as check_license, so an agent can route without opening the schema.

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?

"Use this when the user has a name but no license number" gives a clear triggering condition and implies the inverse case belongs elsewhere. It stops short of naming the alternative tool (check_license) explicitly, so the exclusion is inferred rather than stated.

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