Skip to main content
Glama

BRAINIAC Public Records, Crime & Regulatory Intelligence

List regulatory penalty history

public-records_regulatory-penalty-history
Read-onlyIdempotent

List supplied penalty and fine actions with amounts when present. Missing amounts are not invented. Price $0.04 USDC. POST /api/v1/public-records/regulatory-penalty-history. An unpaid call returns the x402 payment terms and does not run.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "public-records_regulatory-penalty-history"
  }
}

Input Schema

NameRequiredDescriptionDefault
csvNocsv, string, length 0 to 200000. Optional.
asOfNoasOf, string, length 0 to 40. Optional.
feedNofeed, object. Optional.
fileNofile, object. Optional.
jsonNojson, string, length 0 to 200000. Optional.
textNotext, string, length 0 to 200000. Optional.
countryNocountry, string, length 0 to 80. Optional.
noticesNonotices, array. Optional.
incidentsNoincidents, array. Optional.
crimeStatsNocrimeStats, array. Optional.
businessNameNobusinessName, string, length 0 to 200. Optional.
courtRecordsNocourtRecords, array. Optional.
enforcementActionsNoenforcementActions, array. Optional.

Output Schema

NameRequiredDescriptionDefault
itemsNoitems. Array.
statusNostatus. String.
findingsNofindings. Array.
checkedAtNocheckedAt. String.
limitationsNolimitations. Array.
penaltyCountNopenaltyCount. Number.
guiltInferredNoguiltInferred. Boolean.
publicSourcesNopublicSources. Array.
apiKeyRequiredNoapiKeyRequired. Boolean.
paidProviderUsedNopaidProviderUsed. Boolean.
totalPenaltyAmountNototalPenaltyAmount. Number.
chargeTreatedAsConvictionNochargeTreatedAsConviction. Boolean.
allegationTreatedAsJudgmentNoallegationTreatedAsJudgment. Boolean.
investigationTreatedAsGuiltNoinvestigationTreatedAsGuilt. Boolean.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/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 open-world, so the safety profile is covered. The description adds genuinely new behavioral context: a $0.04 USDC price, the POST endpoint, and the fact that an unpaid call returns x402 payment terms without executing. The data-fidelity guarantee ('missing amounts are not invented') is also useful, though the response shape is left to the output schema.

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 short sentences, purpose front-loaded, then the data-fidelity caveat, then cost and endpoint, then the failure mode. Nothing is repeated and every sentence carries information an agent needs before calling.

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?

Payment and fidelity behavior are well covered and an output schema exists, so return values need no explanation. However, for a tool with 13 parameters and deep nesting, the description never says what input the caller must supply to get penalty history, leaving the agent to infer the entire input contract from generic schema labels.

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 the schema is the primary source for all 13 parameters, including the nested enforcementActions, notices, incidents and courtRecords arrays. The description adds no meaning about which inputs drive the penalty list (e.g., that enforcementActions carries penaltyAmount), so it sits at the baseline rather than compensating for the schema's generic field labels.

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?

States a specific verb and resource: list penalty and fine actions with amounts when present. The word 'supplied' hints that it operates over caller-provided records rather than searching a corpus, but the description never contrasts this with the sibling public-records_regulatory-enforcement-search, so the boundary is left implicit.

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

Usage Guidelines2/5

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

No when-to-use or when-not-to-use guidance is given, and no alternative is named. An agent cannot tell from this text whether to call this tool or public-records_regulatory-enforcement-search when it wants penalty data.

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