Skip to main content
Glama

BRAINIAC Public Records, Crime & Regulatory Intelligence

Cross-reference public investigations

public-records_investigation-cross-reference
Read-onlyIdempotent

Cross-reference subjects across court, enforcement, and notice records while preserving non-judgment statuses and never inferring guilt. Price $0.05 USDC. POST /api/v1/public-records/investigation-cross-reference. 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_investigation-cross-reference"
  }
}

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.
subjectCountNosubjectCount. 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?

Annotations already declare readOnly, idempotent, non-destructive and open-world, so the safety bar is lower. The description adds genuinely new behavioral facts: the $0.05 USDC price, the POST endpoint, and critically that an unpaid call returns x402 payment terms and does not execute — an agent needs that to interpret a failed call. It also states the non-inference-of-guilt constraint, which shapes how results should be presented.

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 tight sentences: purpose and constraint first, then cost and endpoint, then payment failure behavior. No filler, and the most decision-relevant information is front-loaded. Slightly dense but well ordered.

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 values need not be described, and the 13 nested parameters are fully documented in the schema. The description covers the remaining gaps an agent would care about: payment model, endpoint, unpaid-call behavior, and the interpretive constraint. Missing only explicit sibling routing, which for a cross-reference tool is a modest gap.

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 effectively complete, so the schema carries the burden and a 3 is the baseline. The description hints at the courtRecords, enforcementActions and notices inputs by naming those record domains, but adds nothing about the other input modes (csv, json, text, file, feed, asOf), so it does not meaningfully extend the schema.

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: cross-referencing subjects across court, enforcement, and notice records, with the distinguishing constraint of preserving non-judgment statuses. An agent can tell this apart from single-source siblings like court-decision-search-normalize or regulatory-enforcement-search, though the description never names an alternative explicitly.

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 implied by 'cross-reference subjects across court, enforcement, and notice records' — use it when you need correlated entities across multiple record types. There is no statement of when not to use it, no prerequisites about supplying the record arrays, and no routing to sibling tools that handle single-source extraction.

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