Skip to main content
Glama

enforcement_actions

Board discipline and unlicensed-activity citations for a state, license number, name, or county. Merges licensed-activity discipline rows and unlicensed-activity citations, newest first. Republished as filed; a citation is an allegation the board acted on, a Final Order is the board's decision.

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": "enforcement_actions"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNoRespondent or DBA name fragment
limitNo
sinceNoISO date, e.g. 2025-01-01
stateYes
countyNoe.g. Miami-Dade
all_tradesNo
license_numberNoe.g. CCC1325838

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/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 reasonably well: it discloses that results merge two distinct sources, are ordered newest first, are 'republished as filed,' and distinguishes a citation (an allegation) from a Final Order (a decision). It omits pagination/truncation behavior and any auth or rate-limit context.

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?

Three dense sentences with the returned-resource statement front-loaded, followed by ordering and record-type semantics. Each sentence carries information, though 'Republished as filed' is slightly opaque and could be tightened.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a 7-parameter read tool with no annotations and no output schema, the description covers what the records mean but not what a returned row contains, how limit/pagination works, or what all_trades toggles. Adequate but with clear gaps an agent would need to guess at.

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 57%, and the description names four of the seven parameters (state, license_number, name, county) as filter dimensions, which matches what the schema already says. It adds no syntax or format detail and is silent on limit, since, and especially all_trades, which has no schema description at all.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names the specific resource (board discipline plus unlicensed-activity citations) and its scope (state, license number, name, or county), which is far more than a tautology. It also implicitly distinguishes itself from the sibling unlicensed_activity by stating it merges both licensed-discipline rows and unlicensed citations, though it never names the sibling outright.

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?

The merge statement hints that this tool is the superset of unlicensed_activity, giving implied routing value, but there is no explicit when-to-use/when-not guidance against siblings like unlicensed_activity, check_license, or search_licensees. Usage must be inferred from the returned-data description.

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