Skip to main content
Glama

newsflash

get_events

Read-onlyIdempotent

Query the deduped news event graph by theme, source, category and time window. Returns events (many articles about one happening collapsed into one), each with a corroboration count and confidence score. This is the primary tool — prefer it over raw articles. For headlines, briefings, or 'what's happening' asks, pass min_sources: 2 (or 3 for high signal) — the raw recency feed is dominated by single-outlet local stories without it. ONE call is normally enough: trust each event's corroboration (distinct outlets), confidence (0-1; 1.0 = fully corroborated), and sources list as-is, and present the top events directly, including each event's url as its link — do NOT call get_event per item or re-verify counts (only drill in when the user wants EVERY outlet's link for one story). The corpus spans 260+ global outlets and a five-year archive (history visible depends on tier).

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

Input Schema

NameRequiredDescriptionDefault
qNoWords to match on headline + summary (whole words, stemmed, any order; every word must appear — when fewer than limit match, the page is filled with any-word matches flagged match: "any")
toNoOnly events active on/before this date. ISO 8601 date/time, e.g. 2026-07-01 or 2026-07-01T00:00:00Z
fromNoOnly events active on/after this date. ISO 8601 date/time, e.g. 2026-07-01 or 2026-07-01T00:00:00Z
limitNoMax events (default 15)
sourceNoSource slug, e.g. 'coindesk' (see list_sources)
categoryNoSource category
semanticNoRank by meaning (embedding similarity) instead of keyword match — requires q; better for concepts ('monetary easing') than exact strings
min_sourcesNoOnly events corroborated by at least this many distinct outlets — use 2-3 for briefings/headlines to skip single-source noise

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / q / description
      Previous value: -"Free-text theme/keyword to match on headline + summary"New value: +"Words to match on headline + summary (whole words, stemmed, any order; every word must appear — when fewer than limit match, the page is filled with any-word matches flagged match: \"any\")"
  2. Changed1 schema field changed
    • changedInput schema / properties / limit / description
      Previous value: -"Max events (default 25)"New value: +"Max events (default 15)"
  3. Changed1 schema field changed
    • addedInput schema / properties / min_sources
      Added value: +{
      +  "description": "Only events corroborated by at least this many distinct outlets — use 2-3 for briefings/headlines to skip single-source noise",
      +  "maximum": 50,
      +  "minimum": 1,
      +  "type": "integer"
      +}
  4. Changed1 schema field changed
    • addedInput schema / properties / semantic
      Added value: +{
      +  "description": "Rank by meaning (embedding similarity) instead of keyword match — requires q; better for concepts ('monetary easing') than exact strings",
      +  "type": "boolean"
      +}
  5. First observed

TDQS

A4.8/5.0
Behavior5/5

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

Annotations only declare the safe-read profile (readOnly, idempotent, not open-world); the description adds the substantive behavior: dedup/corroboration semantics, confidence scale (0-1, 1.0 = fully corroborated), the 260+ outlet / five-year corpus, and tier-dependent history depth. It also warns that the underlying recency feed skews to single-outlet local stories, which is non-obvious and actionable.

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?

Purpose and scope are front-loaded, and the anti-re-verification instruction prevents a costly looping behavior. It is dense but long, with the corpus/tier sentence appended at the end; a few clauses could be tightened without losing meaning.

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?

There is no output schema, and the description compensates by describing the return shape — events with corroboration count, confidence score, sources list, and url — plus how to present them. Combined with the corpus/tier caveat, an agent has enough to call it once and render results correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3; the description earns more by giving operational meaning to min_sources (2 for briefings, 3 for high signal) and by implying that q is driving theme/queries in a deduped graph. It does not add guidance for the date window or source/category interplay beyond what the schema already says.

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?

States a specific verb and resource — 'Query the deduped news event graph' — and immediately defines what an event is ('many articles about one happening collapsed into one'), which separates it from search_articles and get_event. The agent can tell which tool it is without opening the schema.

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?

Explicit routing: 'prefer it over raw articles', 'pass min_sources: 2 (or 3 for high signal)' for briefings/headlines, 'only drill in when the user wants EVERY outlet's link for one story'. It names the alternative behavior (get_event per item) and the condition that would justify it.

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