Skip to main content
Glama

Metis · News Radar — Get News Briefs

get_news_briefs

Retrieve recent news briefs from a database and filter by source type, domain, or date to track updates and research findings.

Instructions

Retrieve recent news briefs from the database.

Args:
    limit: Maximum number of briefs to return (default 10).
    source_type: Filter by type — "news" for RSS items, "article" for scientific papers. Empty = all.
    domain: Filter by domain tag (e.g. "AI", "public-health"). Empty = all.
    since: ISO date string — only return briefs created after this date. Empty = all.

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

Input Schema

NameRequiredDescriptionDefault
limitNo
sinceNo
domainNo
source_typeNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.1/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full behavioral burden. 'Retrieve' implies read-only, but nothing is said about ordering (newest first?), pagination, what happens when limit and since conflict, or how read/unread state relates to mark_brief_read — meaningful gaps for a query tool with zero annotation coverage.

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 core purpose is front-loaded in one sentence, followed by a compact argument list that earns its space by compensating for the empty schema. The Python-docstring 'Args:' formatting is slightly verbose but not wasteful.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

An output schema exists, so return-shape explanation is not required, and all four parameters are covered. What is missing is routing context against a very large sibling set and any note on result ordering — enough to make it merely adequate rather than complete.

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 0%, yet the description documents all four parameters: limit default 10, source_type values ('news' = RSS, 'article' = scientific papers), domain examples ('AI', 'public-health'), and since as an ISO date. It also supplies an implicit enum the schema lacks. Minor gaps remain (inclusive/exclusive date boundary, sort order).

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?

States a specific verb (Retrieve) and resource (news briefs) with a scope qualifier ('recent'). It does not differentiate itself from plausible siblings like get_missed_news, get_daily_insight, or check_news_feeds, which an agent would need in order to choose correctly.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description only enumerates arguments; it never says when to call this versus scanning feeds (scan_news) or fetching missed items (get_missed_news). No prerequisites or exclusions are given, leaving selection entirely to inference from the tool name.

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

Deploy Server

Other Tools