Skip to main content
Glama

Metis ยท News Radar โ€” Generate Daily Insight

generate_daily_insight

Assembles recent activity from agents, news, meetings, and library additions, providing the raw context for the Metis agent to synthesize a daily insight.

Instructions

Assemble recent activity into context for the daily insight.

Gathers the raw material for a "what's happening across your research"
digest: the last 7 days of agent_runs summaries, last 3 days of high-signal
news_briefs, last 14 days of meeting titles, and last 7 days of new library
additions. It stores a placeholder row in daily_insights; the Metis agent
does the actual synthesis from the returned context. Read the stored result
later with get_daily_insight.

Takes no arguments.

Returns:
    A text block of the assembled recent context (and the sources drawn on)
    for the agent to synthesize into a daily insight.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior5/5

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

The description discloses that it stores a placeholder row in daily_insights and that the Metis agent does the actual synthesis. It also details the data sources and time ranges. With no annotations provided, the description fully covers behavioral traits.

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 well-structured, starting with a one-sentence summary, followed by detailed data gathering spec, workflow hint, parameter note, and return description. Every sentence adds value without redundancy.

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?

The description covers the purpose, data sources, workflow, and return value. With an output schema present, it does not need to explain return values in more depth. It could mention error handling, but overall it is 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 no parameters, so the baseline score is 4. The description explicitly states 'Takes no arguments,' which adds no extra meaning beyond the empty schema but is clear.

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 the tool assembles recent activity into context for a daily insight, specifying the exact types and time ranges of data gathered. It distinguishes itself from the sibling tool get_daily_insight by noting that get_daily_insight reads the stored result.

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 provides clear workflow guidance: call this tool to generate the raw context, then use get_daily_insight to retrieve the synthesized result. It does not explicitly state when not to use this tool, but the guidance is adequate.

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