Skip to main content
Glama

Get high-velocity AI news (public)

ic_news_get
Read-only

Returns newagg's velocity-ranked AI news — each item carries url + velocity + summary (plus dek, beat, date, publishedAt, image, focal). This is the RAW aggregator feed (the same firehose that drives the floor10 news kiosk), a DIFFERENT surface from ic_signal_* (which serves THE SIGNAL, the weekly editorial dispatch). Items come back ranked highest-velocity-first (ties keep the feed's own order). No auth required. Args: { limit?: number (1-25, default 20), min_velocity?: number (>=1, default 1 — keep only items corroborated by >= this many sources), q?: string (2-80 chars, case-insensitive substring over title + summary) }.

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

Input Schema

NameRequiredDescriptionDefault
qNoCase-insensitive text to find in title and summary (2-80 chars).
limitNoHow many items to return (1-25, default 20).
min_velocityNoKeep only items corroborated by at least this many sources (default 1).

Output Schema

NameRequiredDescriptionDefault
okNotrue when the call did what it was asked; false with `error` and `error_kind` when it did not
textNoThe tool's reply when it returns plain text instead of JSON
errorNoWhy the call failed, in a sentence a person can act on. Present only when ok is false.
resultNoThe tool's value when it returns a list or a single value instead of an object
error_kindNoMachine-readable failure class: no_token, missing_scope, forbidden, not_found, invalid_input, rate_limited or transient

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "$schema": "http://json-schema.org/draft-07/schema#",
      +  "additionalProperties": {},
      +  "description": "The tool's JSON result. Every field the tool's description names is present at the top level; ok, error and error_kind follow the shared envelope.",
      +  "properties": {
      +    "error": {
      +      "description": "Why the call failed, in a sentence a person can act on. Present only when ok is false."
      +    },
      +    "error_kind": {
      +      "description": "Machine-readable failure class: no_token, missing_scope, forbidden, not_found, invalid_input, rate_limited or transient"
      +    },
      +    "ok": {
      +      "description": "true when the call did what it was asked; false with `error` and `error_kind` when it did not"
      +    },
      +    "result": {
      +      "description": "The tool's value when it returns a list or a single value instead of an object"
      +    },
      +    "text": {
      +      "description": "The tool's reply when it returns plain text instead of JSON"
      +    }
      +  },
      +  "type": "object"
      +}
  2. Changed3 schema fields changed
    • addedInput schema / properties / limit / description
      Added value: +"How many items to return (1-25, default 20)."
    • addedInput schema / properties / min_velocity / description
      Added value: +"Keep only items corroborated by at least this many sources (default 1)."
    • addedInput schema / properties / q / description
      Added value: +"Case-insensitive text to find in title and summary (2-80 chars)."
  3. Changed3 schema fields changed
    • removedInput schema / properties / limit / description
      Removed value: -"How many items to return (1-25, default 20)."
    • removedInput schema / properties / min_velocity / description
      Removed value: -"Keep only items corroborated by at least this many sources (default 1)."
    • removedInput schema / properties / q / description
      Removed value: -"Case-insensitive text to find in title and summary (2-80 chars)."
  4. Changed3 schema fields changed
    • addedInput schema / properties / limit / description
      Added value: +"How many items to return (1-25, default 20)."
    • addedInput schema / properties / min_velocity / description
      Added value: +"Keep only items corroborated by at least this many sources (default 1)."
    • addedInput schema / properties / q / description
      Added value: +"Case-insensitive text to find in title and summary (2-80 chars)."
  5. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations only declare readOnly/openWorld, so the description carries the rest and does well: it discloses the ordering contract ('highest-velocity-first, ties keep the feed's own order'), what fields each item carries, and 'No auth required'. It omits rate limits and volume/freshness characteristics of the feed, which would matter for an agent planning repeated calls.

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?

Front-loaded with purpose, then differentiation, then behavior, then args — a sensible order. It is dense rather than padded, though the parenthetical field list and the full repeated args block overlap heavily with the schema and output schema.

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 read-only, three-optional-param feed with an output schema, the description supplies identity, differentiation, ordering, auth, and parameter defaults — essentially everything needed. Missing only operational context such as feed freshness, update cadence, or expected result volume.

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%, so the baseline is 3, and the args recap in the description largely restates the schema (ranges, defaults, substring behavior). The one genuinely additive gloss is clarifying that min_velocity measures source corroboration, but that phrasing is already present in the schema description.

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 ('Returns newagg's velocity-ranked AI news') and immediately names the sibling family it must not be confused with: 'a DIFFERENT surface from ic_signal_* (which serves THE SIGNAL, the weekly editorial dispatch)'. An agent can route between this and ic_signal_* without opening either schema.

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?

Explicitly frames the tool as the raw aggregator firehose versus the editorial dispatch, which gives clear context for choosing it. It does not spell out a negative case ('do not use when you want curated weekly stories, use ic_signal_get_latest'), so selection still requires a small inference.

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.