Skip to main content
Glama

Offendersearch

by app.offendersearch
OverviewDiscussionsAdmin

map_open_record

Open the complete record behind one map marker, or behind a saved reference.

Returns: { record, recordRef, billing: { billed, unit, reason }, notice }.
`record` is the same Record object search_offenders returns. `recordRef`
('mr_...') is a lasting reference: keep it to open the same record later,
after the marker id has expired.

Billing: one record open per person per map response, at the account's
record-open rate (published price $0.035 per open; an account's agreed rate
may differ) — so open a marker only when the user wants that person's
record, not every marker in a view or along a route.
  - The same marker id again is free (`reason: 'marker_already_opened'`).
  - A new map_viewport, map_area, map_route or map_group answer carries new
    ids; opening the same person from it is a new charge.
  - Opening by `recordRef` is one record open, then free for 24 hours. A
    record just opened from a marker is also free by its reference for 24
    hours.
`billing.billed` says whether THIS open was charged.

Marker ids work for 24 hours (410 `marker_expired` after that). A 410
`record_no_longer_listed` means the registry no longer lists the person; it
is not billed.

Auth: uses the caller's X-API-Key (request header or OFFENDERSEARCH_API_KEY env).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
marker_idYesA marker id ('mk_...') from map_viewport, map_area, map_route or map_group, or a saved record reference ('mr_...') from an earlier map_open_record.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.6/5.0
Behavior4/5

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

No annotations are provided, so the description carries the full burden, and it does: pricing ($0.035/open, account rate may differ), 24-hour marker expiry with 410 marker_expired, 410 record_no_longer_listed being unbilled, and X-API-Key auth. The only real gap is that it doesn't state rate limits or pagination-like concurrency behavior, but for a single-record fetch that is minor.

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?

Front-loaded with purpose and return shape, then grouped under Returns/Billing/Auth labels with bullet sub-cases. It is long for a one-parameter tool, but nearly every sentence carries non-obvious billing or expiry semantics that an agent must know before calling.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

There is no output schema, and the description compensates by spelling out the return envelope ({ record, recordRef, billing: { billed, unit, reason }, notice }), the error codes, the caching windows, and the auth header. Nothing needed to call it correctly is missing.

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% and the schema already documents the mk_/mr_ prefixes and their sources. The description goes beyond it by stating that marker ids expire after 24 hours while recordRef is 'a lasting reference', and by explaining free re-open semantics for each form.

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?

Specific verb+resource: 'Open the complete record behind one map marker, or behind a saved reference.' It also anchors the returned object to a named sibling ('the same Record object search_offenders returns'), so an agent can distinguish it from map_viewport/map_area which return markers rather than records.

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

Usage Guidelines5/5

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

Explicit when/when-not guidance tied to cost: 'open a marker only when the user wants that person's record, not every marker in a view or along a route.' It further enumerates which situations constitute a new charge versus a free re-open.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Offendersearch toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources