Skip to main content
Glama

BRAINIAC Public Records, Crime & Regulatory Intelligence

Build public records evidence report

public-records_evidence-report
Read-onlyIdempotent

Aggregate court, enforcement, crime-stat, incident, notice, litigation, penalty, and cross-reference findings. Distinguishes allegations, charges, and judgments; never infers guilt. Price $0.08 USDC. POST /api/v1/public-records/evidence-report. 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_evidence-report"
  }
}

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
asOfNoasOf. String.
courtNocourt. Array.
statusNostatus. String.
findingsNofindings. Array.
sectionsNosections. Object.
checkedAtNocheckedAt. String.
distinctionNodistinction. Object.
enforcementNoenforcement. Array.
limitationsNolimitations. Array.
guiltInferredNoguiltInferred. Boolean.
publicSourcesNopublicSources. Array.
apiKeyRequiredNoapiKeyRequired. Boolean.
crossReferenceNocrossReference. Array.
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?

Annotations already declare readOnly, idempotent, openWorld, and non-destructive, yet the description adds genuinely new behavior: a fixed $0.08 USDC price, the POST endpoint, and the critical fact that an unpaid call returns x402 payment terms and does not execute. It also discloses an analytical constraint ('distinguishes allegations, charges, and judgments; never infers guilt') that shapes output trustworthiness. It does not cover output size, rate limits, or failure modes beyond payment, keeping it at 4.

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, front-loaded with what gets aggregated, followed by the evidentiary stance, price, endpoint, and payment behavior. No filler or repetition; the payment sentence is doing real work rather than padding.

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?

An output schema exists, so return-shape explanation is unnecessary. Given the tool's complexity (13 params, nested objects, a paid x402 endpoint), the description covers purpose, evidentiary semantics, and payment mechanics adequately. What is missing is any hint about how the many optional input channels combine into the report, which would matter to an agent deciding what to supply.

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% across all 13 top-level parameters, including nested items, so the schema already carries parameter documentation. The description adds no parameter-level meaning (nothing about csv vs json vs text inputs, asOf semantics, or the feed object), so the baseline of 3 applies.

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 opens with a specific verb and resource: 'Aggregate court, enforcement, crime-stat, incident, notice, litigation, penalty, and cross-reference findings.' The enumerated source categories make the scope concrete, and 'evidence report' matches the tool name. It stops short of explicitly distinguishing itself from siblings like investigation-cross-reference or court-case-timeline-extract, so it lands at 4 rather than 5.

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?

Aggregation of findings is implied as the use case, and the payment note tells the agent what to expect on an unpaid call, but there is no explicit statement of when to choose this over the narrower sibling tools (e.g., use this when you need a combined report rather than a single extract). Guidance is implied rather than stated.

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