Skip to main content
Glama

pending_news

Idempotent

Review backend-fetched news awaiting agent normalization: retrieve queued items, ingest relevant claims with stance and severity, and dismiss irrelevant URLs or source IDs before 48-hour expiry.

Instructions

News the backend fetched but did not normalize because reasoning is delegated to you (agent mode). For each relevant item call ingest_event with one_line_claim / stance / severity / affected_symbols; pass the irrelevant ones back here as dismiss_urls. Items leave the queue once ingested or dismissed, and expire after 48h.

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

Input Schema

NameRequiredDescriptionDefault
limitNoMax items to return.
dismiss_urlsNoLegacy version-limited dismissal; ambiguous multi-version URLs require dismiss_source_ids instead.
include_expiredNoExpose preserved unfinished versions older than 48h for explicit source verification/recovery.
dismiss_source_idsNoExact source_snapshot_id values reviewed as irrelevant; future corrections remain eligible.

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv0.68.10
    • addedInput schema / properties / dismiss_source_ids
      Added value: +{
      +  "anyOf": [
      +    {
      +      "items": {
      +        "type": "string"
      +      },
      +      "type": "array"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ],
      +  "default": null,
      +  "description": "Exact source_snapshot_id values reviewed as irrelevant; future corrections remain eligible.",
      +  "title": "Dismiss Source Ids"
      +}
    • changedInput schema / properties / dismiss_urls / description
      Previous value: -"URLs you reviewed and judged irrelevant to the holdings; they won't be offered again."New value: +"Legacy version-limited dismissal; ambiguous multi-version URLs require dismiss_source_ids instead."
    • addedInput schema / properties / include_expired
      Added value: +{
      +  "default": false,
      +  "description": "Expose preserved unfinished versions older than 48h for explicit source verification/recovery.",
      +  "title": "Include Expired",
      +  "type": "boolean"
      +}
  2. Addedv0.45.1

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare a non-destructive, idempotent but mutating operation; the description supplies the reason (items leave the queue once ingested or dismissed) and a 48h expiry, which together explain why readOnlyHint is false. It does not say whether dismissal is permanent or what happens to an item still in flight at expiry beyond the include_expired schema note.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three compact sentences: what the queue is, the action per item, then the lifecycle/expiry rule. The purpose and the routing instruction are front-loaded with no filler.

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?

With an output schema present and full parameter coverage, the description only needs to convey the agent-mode workflow and queue lifecycle, and it does both. The remaining ambiguity (what counts as relevant) is the delegated judgment the tool exists to support, not a definition gap.

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 limit, dismiss_urls, dismiss_source_ids, and include_expired are already documented, including the legacy-versus-exact-id distinction. The description only reinforces dismiss_urls usage and adds no format or precedence guidance beyond the schema.

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 resource and its state: news fetched but deliberately left un-normalized because reasoning is delegated to the agent. This distinguishes it clearly from ingest_event (the sink for judged items) and from collection-oriented siblings like collect_news.

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?

Gives an explicit per-item decision rule: relevant items go to ingest_event with one_line_claim/stance/severity/affected_symbols, irrelevant ones come back here as dismiss_urls. It does not cover when to use limit, include_expired, or dismiss_source_ids versus dismiss_urls, so the caller must fall back on schema text for those choices.

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