Skip to main content
Glama

Swapwire

Get a contractor license record

get_license
Read-onlyIdempotent

Full record for one contractor license by number: status, license types, bond, insurance, workers' comp, discipline, complaints and citations where published, city permits, and the agency source link. California is the default; pass state for others. Use this when you have a license number, or after search_licenses to read a match in full (use the id it returns).

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

Input Schema

NameRequiredDescriptionDefault
stateNoTwo-letter state code. Default CA. Others with data: CO, CT, FL, IL, KS, MN, NY, OR, PA, TX, VA, WA.
license_numberYesLicense number as the agency prints it, or the id from search_licenses, e.g. "1154967" (CA) or "CGC047089" (FL).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, and closed-world, so the safety profile is covered. The description adds useful context beyond that: the record is a full read, some sub-records appear only 'where published' (so fields may be absent), and California is the implicit default state. It doesn't mention not-found behavior or rate limits, which keeps it from 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.

Conciseness4/5

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

Two sentences, front-loaded with the returned-content summary and followed by usage routing. The long field enumeration is dense but justified given there is no output schema; no filler text.

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, the description correctly enumerates the return fields, and annotations cover the safety profile, so an agent has enough to call it correctly. Minor gaps remain around not-found behavior and whether some sub-records vary by state, but nothing essential is missing.

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 both parameters are already documented, including the CA default and the example formats. The description mostly restates the default-state behavior and the search_licenses id reuse already present in the schema, adding little new meaning. Baseline 3 applies.

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?

Specific verb+resource: fetches the full record for one contractor license by number, and enumerates what the record contains (status, license types, bond, insurance, workers' comp, discipline, complaints, citations, permits, source link). This clearly distinguishes it from search_licenses, which returns matches rather than a full record.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

States explicit trigger conditions: use it when you already have a license number, or after search_licenses to read a match in full using the returned id. The alternative (search_licenses) and the handoff between them are both named, leaving little to inference.

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