Skip to main content
Glama
Sign In

FXMacroData

by io.github.fxmacrodata
OverviewDiscussionsAdmin

Geopolitical Event Revisions

geopolitical_event_revisions
Read-only

Bounded source-record revisions available by a historical cutoff.

Input Schema

NameRequiredDescriptionDefault
as_ofNoKnowledge cutoff with timezone, e.g. 2024-06-30T23:59:59Z; omit for latest.
limitNoMaximum rows per page, 1-100.
offsetNoZero-based row offset; 0 starts the first page.
event_idYesEvent ID from history results: exactly 64 lowercase hexadecimal characters.

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed8 schema fields changed
    • removedInput schema / properties / as_of / anyOf
      Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
    • removedInput schema / properties / as_of / default
      Removed value: -null
    • addedInput schema / properties / as_of / description
      Added value: +"Knowledge cutoff with timezone, e.g. 2024-06-30T23:59:59Z; omit for latest."
    • addedInput schema / properties / as_of / type
      Added value: +[
+  "string",
+  "null"
+]
    • addedInput schema / properties / event_id / description
      Added value: +"Event ID from history results: exactly 64 lowercase hexadecimal characters."
    • addedInput schema / properties / limit / description
      Added value: +"Maximum rows per page, 1-100."
    • addedInput schema / properties / offset / description
      Added value: +"Zero-based row offset; 0 starts the first page."
    • removedInput schema / title
      Removed value: -"geopolitical_event_revisionsArguments"
  2. Added

TDQS

C2.8/5.0
Behavior3/5

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

Annotations already establish read-only, non-destructive, open-world behavior. The description adds the useful point-in-time notion of a historical cutoff, but it does not explain what "source-record revisions" represent or how the bounded result behaves.

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?

It is a single concise sentence with no wasted wording. The fragmentary phrasing is efficient but somewhat under-specified.

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

Completeness2/5

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

For a tool that requires an event_id and exposes paginated revisions with an output schema, the description does not explain what revisions are, how they relate to the event_id, or when this should be used instead of adjacent tools. It leaves too much to schema inference.

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 all four parameters already carry detailed meaning, including event_id and as_of. The description only loosely echoes the as_of cutoff and adds no meaningful interpretation beyond the schema.

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

Purpose3/5

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

The description identifies the resource as "source-record revisions" and mentions a "historical cutoff," but it lacks a clear action verb such as list or retrieve and does not explicitly tie the revisions to a geopolitical event. It remains only vaguely distinguishable from siblings like geopolitical_history or geopolitical_event.

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?

There is no guidance on when to use this tool versus geopolitical_event, geopolitical_history, or geopolitical_sources. The historical cutoff hint is not enough to tell an agent which tool to select.

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

All FXMacroData 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