Skip to main content
Glama

unlicensed_activity

List people and companies the state board cited for unlicensed contracting, filtered by county and/or name. Use when the user has a name or company from a truck or flyer but no license number, or asks who was caught working unlicensed after a storm. Republished as filed; a citation is not a judgment. Defaults to roofing-typed citations; set all_trades=true for all construction trades.

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>"
    },
    "name": "unlicensed_activity"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNoRespondent or DBA name fragment
limitNo
stateYes
countyNoe.g. Lee, Miami-Dade, Dade — normalized automatically
all_tradesNofalse (default) = roofing-typed citations only; true = all trades

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/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 disclose two high-value traits: the default is roofing-typed citations only (all_trades=true to widen), and the data is 'republished as filed; a citation is not a judgment.' It omits return field shape, pagination behavior for limit, and any auth/scope notes, which keeps it below 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.

Conciseness5/5

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

Four tight sentences ordered purpose → when-to-use → caveat → default behavior. The most error-prone fact (roofing-only default) is called out explicitly, and no sentence is filler.

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?

Covers purpose, triggering conditions, data caveat, and the non-obvious default for a 5-parameter tool with no annotations and no output schema. The main gap is that an agent gets no sense of what a citation record contains or how results are ordered/paged.

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 coverage is 60%, and the description reinforces name and county filtering plus the all_trades default semantics, adding real value. However the required 'state' parameter and 'limit' get no explanation in either the description or the schema, so the description does not fully compensate for the coverage gap.

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: 'List people and companies the state board cited for unlicensed contracting,' with the filter scope (county and/or name) stated immediately. It is clearly distinguishable from license-lookup siblings because the description frames it as the citation/enforcement record set rather than a license record.

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 concrete triggering conditions: 'user has a name or company from a truck or flyer but no license number' and 'who was caught working unlicensed after a storm.' This implicitly routes away from check_license/search_licensees, though it never names those siblings explicitly and states no exclusions.

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