Skip to main content
Glama

BRAINIAC Public Records, Crime & Regulatory Intelligence

Compare public crime statistics

public-records_crime-statistics-compare
Read-onlyIdempotent

Compare supplied official crime counts or rates across periods for the same offense and area. Missing values are not invented. Price $0.04 USDC. POST /api/v1/public-records/crime-statistics-compare. 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_crime-statistics-compare"
  }
}

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

A4.4/5.0
Behavior4/5

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

The annotations already establish read-only, idempotent, open-world, and non-destructive behavior. The description adds important operational context: missing values are not invented, the cost is $0.04 USDC, and an unpaid call returns x402 payment terms without running.

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?

The description is four tight sentences with the purpose front-loaded. Every sentence carries useful information: comparison semantics, missing-data behavior, price, endpoint, and unpaid-call behavior.

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?

For a 13-parameter nested tool with an output schema, the description covers the essential purpose, key constraint, pricing, and payment gate. It does not explain how to supply data via the optional csv, json, text, file, or feed containers, but the schema coverage and output schema compensate substantially.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3. The description adds meaningful semantics beyond the schema by clarifying that counts or rates are compared across periods for the same offense and area, and that missing values are not fabricated.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific verb and resource: compare supplied official crime counts or rates across periods for the same offense and area. The word 'supplied' and the comparison framing distinguish it from sibling search/extract tools without needing named alternatives.

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

Usage Guidelines4/5

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

It gives clear usage context: the tool compares supplied crime counts or rates across periods for the same offense and area. It does not explicitly name alternatives or when not to use it, so it falls short of the top score.

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