Skip to main content
Glama

BRAINIAC Public Records, Crime & Regulatory Intelligence

Extract police public notices

public-records_police-notice-extract
Read-onlyIdempotent

Extract structured fields and wording signals from supplied police or public safety notices without inferring guilt. Price $0.03 USDC. POST /api/v1/public-records/police-notice-extract. 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_police-notice-extract"
  }
}

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.
noticeCountNonoticeCount. 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

B3.3/5.0
Behavior4/5

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

Annotations already cover read-only, idempotent, open-world and non-destructive, so the safety profile is known. The description still adds real value beyond them: the no-guilt-inference constraint, the $0.03 USDC price, the POST endpoint, and crucially that an unpaid call only returns x402 payment terms and does not execute. That payment-gate behavior is not derivable from any structured field.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three short sentences, front-loaded with purpose, then mechanics. However the middle sentence is a webhook-style implementation detail (route path) that is fully redundant with the tool's transport and the last sentence mixes the payment gate with the endpoint spec; some of this is structured-field duplication rather than added value.

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?

Output schema and rich annotations mean return values and safety need not be explained, so the description is roughly adequate. But for a tool with 13 heterogeneous input shapes, omitting how inputs are combined or which one is preferred leaves a genuine gap an agent cannot close from structured fields alone.

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 per-parameter meaning is already documented and the baseline of 3 applies. The description adds nothing about the 13 inputs — notably not which of text, csv, json, file, feed, or the notices/incidents arrays is the intended carrier, which is the main ambiguity in 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: 'Extract structured fields and wording signals from supplied police or public safety notices', plus a scope constraint ('without inferring guilt'). This clearly separates it from siblings like crime-statistics-compare or regulatory-enforcement-search, which search rather than extract. It stops short of a 5 only because it never contrasts itself with a sibling by name.

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?

'From supplied ... notices' weakly implies the caller already holds the content, but there is no explicit when-to-use, no exclusion, and no named alternative among the nine sibling tools. An agent must infer context from the name alone.

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