Skip to main content
Glama

Geotone — Global News Signals

The live wire

get_wire
Read-only

The live wire: the world's most significant stories right now, ranked by a published formula (authority-weighted outlet breadth, boosted by consequence themes, coded events, and casualty figures, decayed by recency over 72h). Each story carries one representative link, outlet count, tone, countries, non-English source languages that also reported the event, and a chain_id when it belongs to a multi-day story timeline (fetch with get_story_chain). Reclustered every 2 hours.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoMax stories to return (default 20)

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
metaNo
pageNo
storiesYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedOutput schema / properties / stories / items / properties / languages
      Added value: +{
      +  "items": {
      +    "type": "string"
      +  },
      +  "type": "array"
      +}
  2. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "additionalProperties": true,
      +  "properties": {
      +    "meta": {
      +      "properties": {
      +        "attribution": {
      +          "type": "string"
      +        },
      +        "license": {
      +          "type": "string"
      +        },
      +        "source": {
      +          "type": "string"
      +        }
      +      },
      +      "type": "object"
      +    },
      +    "page": {
      +      "type": "string"
      +    },
      +    "stories": {
      +      "items": {
      +        "additionalProperties": true,
      +        "properties": {
      +          "chainId": {
      +            "type": [
      +              "number",
      +              "null"
      +            ]
      +          },
      +          "countries": {
      +            "items": {
      +              "type": "string"
      +            },
      +            "type": "array"
      +          },
      +          "domain": {
      +            "type": "string"
      +          },
      +          "firstSeen": {
      +            "type": "string"
      +          },
      +          "lastSeen": {
      +            "type": "string"
      +          },
      +          "meta": {
      +            "properties": {
      +              "attribution": {
      +                "type": "string"
      +              },
      +              "license": {
      +                "type": "string"
      +              },
      +              "source": {
      +                "type": "string"
      +              }
      +            },
      +            "type": "object"
      +          },
      +          "outlets": {
      +            "type": "number"
      +          },
      +          "rank": {
      +            "type": "number"
      +          },
      +          "related": {
      +            "items": {
      +              "additionalProperties": true,
      +              "properties": {
      +                "meta": {
      +                  "properties": {
      +                    "attribution": {
      +                      "type": "string"
      +                    },
      +                    "license": {
      +                      "type": "string"
      +                    },
      +                    "source": {
      +                      "type": "string"
      +                    }
      +                  },
      +                  "type": "object"
      +                },
      +                "outlets": {
      +                  "type": "number"
      +                },
      +                "title": {
      +                  "type": "string"
      +                },
      +                "url": {
      +                  "type": "string"
      +                }
      +              },
      +              "type": "object"
      +            },
      +            "type": "array"
      +          },
      +          "timeline": {
      +            "type": [
      +              "string",
      +              "null"
      +            ]
      +          },
      +          "title": {
      +            "type": "string"
      +          },
      +          "toneAvg": {
      +            "type": "number"
      +          },
      +          "topic": {
      +            "type": [
      +              "string",
      +              "null"
      +            ]
      +          },
      +          "url": {
      +            "type": "string"
      +          }
      +        },
      +        "type": "object"
      +      },
      +      "type": "array"
      +    }
      +  },
      +  "required": [
      +    "stories"
      +  ],
      +  "type": "object"
      +}
  3. First observed

TDQS

A4.2/5.0
Behavior3/5

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

Annotations already mark readOnlyHint=true and openWorldHint=false, so the agent knows it's a read operation with a bound data set. The description adds useful detail like the ranking formula, 72-hour decay, and 2-hour update cycle. However, it doesn't clarify if or when the output changes between calls, or potential behavior under high-load conditions, which would be helpful for a news feed tool.

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 description is a single paragraph of around 50 words, which is concise for the amount of information it conveys. Every sentence adds value: purpose, formula, fields, sibling reference, update cadence. Minor waste could be trimmed (e.g., 'non-English') but overall efficient.

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?

Given the complexity (single parameter with full schema coverage, output schema exists, read-only annotation) the description is remarkably complete. It explains the ranking algorithm, lists returned fields, defines chain_id connection to get_story_chain, and states the update cycle. No gaps remain for an agent to select or invoke this tool correctly.

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 the schema already fully documents the limit parameter with its min, max, and default. The description does not add further semantics beyond what the schema provides (e.g., no hint on what the default 20 means in context of story priority). Baseline 3 is appropriate as the schema is already complete.

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 explicitly states the tool retrieves significant current stories ranked by a published formula, listing key fields like outlet count, tone, countries, and chain_id. It clearly distinguishes itself from siblings like get_story_chain and get_trending by focusing on a ranked live feed of breaking stories.

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?

The description provides specific guidance on when to use this tool versus alternatives: it mentions the chain_id field for multi-day stories and refers to get_story_chain for fetching story timelines. It also notes the 72-hour recency decay and 2-hour reclustering schedule, helping the agent know when to re-query.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources