Skip to main content
Glama

FirmTape Geo - public records of world events

by com.firmtape
OverviewDiscussionsAdmin

geo_records

The records themselves, newest first: government advisories and sanctions, flight restrictions, maritime warnings, internet and grid outages, conflict, disaster and attention records. Up to a year back, each with its source, its link, its publication time and the time we first saw it, all UTC. Ask for one exact record with uid. For how many rather than which, call geo_activity; for one country in one call, geo_snapshot. Context, never a trading signal.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
qNowords in the title
uidNoone record id, or several separated by commas; ignores the time window
feedNofeed id, or several separated by commas; the ids are listed by geo_sources
limitNo1 to 200, default 50
sinceNoISO 8601 UTC start; default 7 days ago
untilNoISO 8601 UTC end; default now
cursorNothe next_cursor of a previous call
sectorNogov, air, gps, sea, internet, ground, space or attention
countryNoISO 3166-1 alpha-2, e.g. IR
min_severityNo1 keeps everything, 2 is notable and above, 3 is critical only

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changed
    • changedInput schema / properties / feed / description
      Previous value: -"feed id or comma-separated ids, see geo_sources"New value: +"feed id, or several separated by commas; the ids are listed by geo_sources"
    • changedInput schema / properties / min_severity / description
      Previous value: -"2 = notable and above, 3 = critical only"New value: +"1 keeps everything, 2 is notable and above, 3 is critical only"
    • addedInput schema / properties / sector / description
      Added value: +"gov, air, gps, sea, internet, ground, space or attention"
    • addedInput schema / properties / uid
      Added value: +{
+  "description": "one record id, or several separated by commas; ignores the time window",
+  "type": "string"
+}
  2. First observed

TDQS

A4.4/5.0
Behavior4/5

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

With no annotations, the description carries the burden of behavioral disclosure. It states ordering ('newest first'), time range ('up to a year back'), timezone ('all UTC'), and record contents (source, link, publication time, first-seen time). It also discloses that uid is for exact records. It does not mention pagination limits or rate limits, but the schema covers cursor/limit; the key behavioral traits are disclosed.

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 compact: three sentences. It front-loads the core purpose ('records themselves, newest first'), then lists categories and record fields, then routes to siblings. No fluff; every sentence earns its place.

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 10-parameter tool with no output schema and no annotations, the description covers the essential context: record types, ordering, time window, fields, and sibling relationships. It does not spell out the exact response JSON, but it enumerates the record fields, which is sufficient. Pagination is implied by the schema (cursor), and severity semantics are in the schema. Overall, it is nearly complete, missing only explicit response format details.

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 coverage is 100%, so every parameter already has a description. The description adds minimal parameter-specific meaning—only reinforcing uid usage ('Ask for one exact record with uid') and the existence of a 'q' for title words is not expanded. Baseline 3 is appropriate since the schema does the heavy lifting and the description does not go beyond it.

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 clearly states it returns 'records themselves' and enumerates the types of records (advisories, sanctions, flight restrictions, etc.), establishing a specific resource. It also distinguishes itself from geo_activity (counts) and geo_snapshot (one country), so an agent can immediately tell it apart from siblings.

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?

Explicitly provides when-not guidance: 'For how many rather than which, call geo_activity; for one country in one call, geo_snapshot.' It also adds an interpretive caveat ('Context, never a trading signal') helping the agent know how to use results. This is clear, actionable routing.

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

All FirmTape Geo - public records of world events 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