Skip to main content
Glama

generate_daily_insight

Assembles recent research activity summaries, news briefs, meeting titles, and library additions into a context block 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
Behavior4/5

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

Describes the data sources used (specific time windows for agent_runs, news_briefs, meetings, library additions) and side effects (stores a placeholder row in daily_insights). No annotations exist, so the description carries full burden and does so adequately.

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 description is front-loaded with the main purpose and uses a bullet-like structure for readability. While it lists specific time ranges per data source, this is necessary context and not wasted. Could be slightly more concise but remains efficient.

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?

Given zero parameters and the presence of an output schema, the description fully explains what the tool does, what data it gathers, what it stores, and how to retrieve the final synthesis. No gaps remain.

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?

No parameters exist, so the description correctly states 'Takes no arguments.' With zero params, the baseline is 4 per rules, and no additional explanation is needed.

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?

Clearly states the verb 'assemble' and resource 'recent activity into context for the daily insight'. Distinguishes from sibling `get_daily_insight` by explaining that this tool gathers raw material and stores a placeholder, while the sibling reads the synthesized 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?

Explains when to use (to get context for a daily insight digest) and suggests using `get_daily_insight` to read the stored result. While it doesn't explicitly list exclusions, the context is clear given the tool's narrow scope.

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