Skip to main content
Glama
SVerITG

Metis

by SVerITG
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Metis · News Radar — Get News Briefs

get_news_briefs

Retrieve recent news briefs from the database, filtered by source type, domain tag, or creation date, to surface RSS items and scientific papers for research monitoring.

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. "HAT", "AI", "public-health"). Empty = all.
    since: ISO date string — only return briefs created after this date. Empty = all.

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

A3.5/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full burden. It adequately describes the read operation but does not disclose potential side effects, permissions, or rate limits. It is clear but not deeply transparent.

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?

The description is extremely concise: a one-sentence purpose followed by a clean bullet-list of parameter details. No extraneous information or repetition.

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?

Given the presence of an output schema (no need to describe return values) and 4 parameters, the description adequately covers parameter usage. It misses typical use cases or examples, but is sufficient for a simple retrieval tool.

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?

With 0% schema description coverage, the description fully compensates by explaining each parameter's purpose, default values, and allowed values (e.g., 'news' vs 'article' for source_type). It adds meaning beyond the schema's raw title fields.

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?

The description clearly states 'Retrieve recent news briefs from the database' with a specific verb and resource. However, it does not explicitly distinguish from sibling tools like 'scan_news' or 'get_new_publications', which could cause ambiguity.

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?

No guidance is provided on when to use this tool versus alternatives (e.g., scan_news for RSS, search_literature for articles). There is no mention of prerequisites or exclusions.

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