Skip to main content
Glama

Metis · News Radar — Full Scan

full_scan

Run all update scans together to get a combined report of new news items, PDFs, unprocessed inbox items, and changed files. No LLM required.

Instructions

Run all Metis update scans in sequence and return a combined report.

Runs:
1. News feeds (RSS) — new items added to news_briefs
2. Literature folder — new PDFs registered in literature_metadata
3. Inbox — unprocessed items flagged
4. Tracked files — changed files reported

No LLM calls. Safe to run at any time.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior4/5

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

With no annotations, the description carries full burden. It discloses that the tool makes no LLM calls and is safe, but it does not detail potential latency or side effects. The step breakdown adds trust.

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 concise, with two short paragraphs. The numbered list of steps is well-structured and easy to parse.

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 zero parameters and the presence of an output schema, the description adequately covers the tool's purpose and behavior. It could mention error handling or time expectations but is otherwise 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?

The tool has zero parameters, so the description need not explain any. Baseline 4 applies.

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?

The description clearly states it runs all Metis update scans in sequence and returns a combined report, listing four specific scan types. This distinguishes it from individual scan tools like scan_news and scan_literature.

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?

The description notes it is safe to run at any time and makes no LLM calls, implying it can be used freely. However, it does not explicitly contrast with separate scan tools or state when to use the full scan vs. individual scans.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/SVerITG/Metis'

If you have feedback or need assistance with the MCP directory API, please join our Discord server