Skip to main content
Glama
Sign In

GeoQuant Orb

by dev.pages.geoquant-orb
OverviewDiscussionsAdmin

[core] news live

get_news_live
Read-only

Live headlines (public RSS feeds: BBC, Al Jazeera, DW, Guardian, NYT, Sky, CBS, CNBC, Euronews etc.; GDELT optional secondary; source per item), multi-topic tags: ukraine, east_flank, black_sea, hormuz, compliance, palantir, space, markets, energy, crypto; geopolitics only as fallback. Call this when you need fresh headlines with links on one of those topics.

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_news_live"
  }
}

Input Schema

NameRequiredDescriptionDefault
topicNoukraine (alias war), east_flank (nato/drones), black_sea (shipping), hormuz (oil), compliance (sanctions/aml), palantir (killchain/ai_military), space, markets, energy, crypto, geopolitics (only headlines matching nothing else)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / topic / description
      Previous value: -"optional topic: ukraine (alias war), east_flank (nato/drones), black_sea (shipping), hormuz (oil), compliance (sanctions/aml), palantir (killchain/ai_military), space, markets, energy, crypto, geopolitics (only headlines matching nothing else); omit for all topics"New value: +"ukraine (alias war), east_flank (nato/drones), black_sea (shipping), hormuz (oil), compliance (sanctions/aml), palantir (killchain/ai_military), space, markets, energy, crypto, geopolitics (only headlines matching nothing else)"
  2. Changed1 schema field changed
    • changedInput schema / properties / topic / description
      Previous value: -"ukraine (alias war), east_flank (nato/drones), black_sea (shipping), hormuz (oil), compliance (sanctions/aml), palantir (killchain/ai_military), space, markets, energy, crypto, geopolitics (only headlines matching nothing else)"New value: +"optional topic: ukraine (alias war), east_flank (nato/drones), black_sea (shipping), hormuz (oil), compliance (sanctions/aml), palantir (killchain/ai_military), space, markets, energy, crypto, geopolitics (only headlines matching nothing else); omit for all topics"
  3. Changed1 schema field changed
    • changedInput schema / properties / topic / description
      Previous value: -"optional topic: ukraine (alias war), east_flank (nato/drones), black_sea (shipping), hormuz (oil), compliance (sanctions/aml), palantir (killchain/ai_military), space, markets, energy, crypto, geopolitics (only headlines matching nothing else); omit for all topics"New value: +"ukraine (alias war), east_flank (nato/drones), black_sea (shipping), hormuz (oil), compliance (sanctions/aml), palantir (killchain/ai_military), space, markets, energy, crypto, geopolitics (only headlines matching nothing else)"
  4. Changed1 schema field changed
    • changedInput schema / properties / topic / description
      Previous value: -"ukraine (alias war), east_flank (nato/drones), black_sea (shipping), hormuz (oil), compliance (sanctions/aml), palantir (killchain/ai_military), space, markets, energy, crypto, geopolitics (only headlines matching nothing else)"New value: +"optional topic: ukraine (alias war), east_flank (nato/drones), black_sea (shipping), hormuz (oil), compliance (sanctions/aml), palantir (killchain/ai_military), space, markets, energy, crypto, geopolitics (only headlines matching nothing else); omit for all topics"
  5. Changed2 schema fields changed
    • addedInput schema / properties / topic / description
      Added value: +"ukraine (alias war), east_flank (nato/drones), black_sea (shipping), hormuz (oil), compliance (sanctions/aml), palantir (killchain/ai_military), space, markets, energy, crypto, geopolitics (only headlines matching nothing else)"
    • changedInput schema / properties / topic / enum
      Previous value: -[
-  "hormuz",
-  "energy",
-  "crypto",
-  "geopolitics"
-]New value: +[
+  "ukraine",
+  "east_flank",
+  "black_sea",
+  "hormuz",
+  "compliance",
+  "palantir",
+  "space",
+  "markets",
+  "energy",
+  "crypto",
+  "geopolitics",
+  "war",
+  "nato",
+  "drones",
+  "shipping",
+  "oil",
+  "sanctions",
+  "aml",
+  "killchain",
+  "ai_military"
+]
  6. First observed

TDQS

A3.9/5.0
Behavior4/5

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

The annotations already declare readOnlyHint=true and openWorldHint=true, and the description adds useful behavioral context: public RSS sources, GDELT as optional secondary, source attribution per item, and the geopolitics fallback rule. It still does not discuss rate limits, failures, or default behavior when no topic is supplied.

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?

The definition is front-loaded with the main purpose and then the topic tags and fallback rule. The source list and repeated topic enumeration make it somewhat dense, but the content is generally useful and not padded with irrelevant text.

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 simple read-only, one-optional-parameter news tool with no output schema, the description covers sources, topic behavior, fallback logic, and the headline-with-links return shape well enough. The main missing piece is what happens when no topic is passed and how results are ordered or limited.

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 the single optional topic parameter already has a detailed enum description with aliases and fallback guidance. The description repeats the topic list and fallback rule but does not explain what happens when topic is omitted, so it adds limited meaning beyond the schema.

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?

The description clearly states that this tool returns live headlines, names the underlying public RSS sources, and lists supported topic tags. It is specific about the resource and scope, but it does not explicitly differentiate itself from sibling news tools such as get_news_radar or get_news_snapshot.

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 a direct usage instruction: call this when you need fresh headlines with links on one of the listed topics. It also notes that geopolitics should be used only as a fallback. However, it does not say when to choose this over the other news-related sibling tools.

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

All GeoQuant Orb 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