Skip to main content
Glama
Sign In

Gemral Edge

by io.github.gemral-edge
OverviewDiscussionsAdmin

Upcoming Catalysts & Scheduled Events

get_upcoming_catalysts

Query upcoming high-impact catalysts and macro events scheduled or anticipated across 4 Event Classes (SCHEDULED, PRECURSOR, DEADLINE, UNEXPECTED). Returns event time, priority score, and impacted tickers.

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": "get_upcoming_catalysts"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMaximum number of catalysts to return
event_classNoFilter by event classification

Output Schema

NameRequiredDescriptionDefault
noticeNoFree-tier upgrade notice; only when results are masked/delayed.
resultsYesTool result payload (read-only evidence). Shape varies by tool; scoring weights are never exposed.
history_limitNoPresent when the license limits history depth: earliest_allowed date, history_days and how many older items were removed.
deprecated_fieldsNoPresent only while a renamed key is still returned next to its replacement: field (old key), replacement (new key, same value), removal (ISO date after which the old key is gone).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedOutput schema / properties / deprecated_fields
      Added value: +{
+  "description": "Present only while a renamed key is still returned next to its replacement: field (old key), replacement (new key, same value), removal (ISO date after which the old key is gone).",
+  "items": {
+    "additionalProperties": true,
+    "type": "object"
+  },
+  "type": "array"
+}
  2. First observed

TDQS

B3.2/5.0
Behavior3/5

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

The description frames this as a pure read ('Query ... Returns event time, priority score, and impacted tickers'), while annotations declare readOnlyHint=false; the tool could have side effects the description never mentions, and that tension is left unresolved. On the plus side, openWorldHint=false is consistent with a curated event database, and no destructive behavior is implied. A 3 reflects useful scoping detail but a notable unaddressed annotation signal.

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?

Two compact sentences, well front-loaded with the core action and scope. The return-value clause is redundant given an output schema exists, but it is brief and does not bloat the text.

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?

Because an output schema exists, the description need not explain return values, so its remaining obligations are purpose, selection guidance, and any behavioral caveats. Purpose is covered, but the missing sibling routing and the unexplained readOnlyHint=false leave gaps for a tool in a dense cluster of event-related siblings.

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% and both parameters (limit, event_class with full enum) are documented in the schema. The description restates the four event class names from the enum and says nothing new about limit semantics, ordering, or default behavior beyond what the schema provides. Baseline 3 is appropriate.

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: query upcoming high-impact catalysts and macro events, including the four event classes and the fields returned. It does not name or contrast any sibling, so an agent cannot tell from this text alone whether get_precursor_signals or get_event_countdown is the better fit.

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 versus alternatives such as get_precursor_signals, get_event_countdown, or get_event_expected_impact, all of which sound closely overlapping. No exclusions, prerequisites, or time-window semantics are given.

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

All Gemral Edge 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