Skip to main content
Glama

BRAINIAC Public Records, Crime & Regulatory Intelligence

Normalize court decision records

public-records_court-decision-search-normalize
Read-onlyIdempotent

Normalize supplied court records and label allegation, investigation, charge, and judgment statuses separately. Guilt is never inferred. Price $0.05 USDC. POST /api/v1/public-records/court-decision-search-normalize. 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_court-decision-search-normalize"
  }
}

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.
recordCountNorecordCount. Number.
guiltInferredNoguiltInferred. Boolean.
publicSourcesNopublicSources. Array.
apiKeyRequiredNoapiKeyRequired. Boolean.
paidProviderUsedNopaidProviderUsed. Boolean.
chargeTreatedAsConvictionNochargeTreatedAsConviction. Boolean.
allegationTreatedAsJudgmentNoallegationTreatedAsJudgment. Boolean.
investigationTreatedAsGuiltNoinvestigationTreatedAsGuilt. Boolean.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

The annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint, so the safety profile is covered by structured data. The description adds real behavioral context beyond that: the semantic guarantee that guilt is never inferred, the separate labeling of four legal statuses, the $0.05 USDC price, the POST endpoint, and the fact that an unpaid call returns x402 payment terms and does not execute. What it does not disclose is whether normalization mutates or returns records, or any rate/limit behavior.

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?

Four short sentences, purpose front-loaded, then the epistemic guarantee, then the pricing and transport facts. Nothing is redundant with the title. The payment sentence is slightly dense, packing price, endpoint and x402 failure mode into one line, but no sentence is wasted.

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?

The tool is complex (13 params, deep nesting, open-world), but annotations cover the safety profile and an output schema exists, so return values need not be explained. Purpose, the status-labeling semantics and the payment behavior are all covered. The remaining gap is guidance on which input channel to populate, which matters given five alternative input shapes.

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 every one of the 13 parameters is documented in the schema, including nested notices, incidents, crimeStats, courtRecords and enforcementActions items. The description adds no meaning about the multiple interchangeable input channels (csv vs json vs text vs file vs feed), which is the one genuinely ambiguous choice for a caller. Baseline 3 is appropriate when the schema carries the parameter burden.

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 a specific verb ('Normalize') and resource ('supplied court records') and adds the distinctive scope of labeling allegation, investigation, charge and judgment statuses separately. That scope separates it from sibling extract/search tools without naming any of them directly. It is clear, though sibling differentiation is left to inference from the sibling names rather than stated.

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?

Usage is only implied: an agent can infer it should call this when it already has raw court records that need status normalization and legal-status separation. No when-not condition, no prerequisite input-shape guidance, and no reference to alternatives such as the timeline-extract or litigation-history tools. The one concrete operating condition given is the payment path ('An unpaid call returns the x402 payment terms and does not run'), which is a call-flow rule rather than selection guidance.

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