Skip to main content
Glama

generate_daily_insight

Collects recent agent runs summaries, news briefs, meeting titles, and library additions into a single context block for agent synthesis of 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
Behavior3/5

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

The description explains that the tool stores a placeholder row in daily_insights and that the Metis agent performs the actual synthesis. It does not detail side effects like overwriting behavior, idempotency, or required permissions. Since no annotations are provided, the description carries the full burden for behavioral transparency, but it is adequate for a tool with no parameters.

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 and well-structured. The first sentence immediately states the purpose, followed by a clear bulleted list of gathered data. It efficiently covers what the tool does, its side effect, and the return value without any extraneous detail.

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 the tool's simplicity (no parameters, clear output), the description is complete. It explains the data sources, the placeholder storage, and the relationship to get_daily_insight. The return value is described, and the presence of an output schema is noted in the context, so the description suffices.

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 input schema has zero parameters, and the description explicitly states 'Takes no arguments.' This adds clarity beyond the schema, confirming there are no inputs needed. With 100% schema description coverage, the baseline is 3, but the explicit statement earns a 4.

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. It specifies the exact sources and timeframes (e.g., last 7 days of agent_runs, last 3 days of news_briefs). It distinguishes itself from the sibling tool get_daily_insight by explaining that this tool prepares the context while get_daily_insight retrieves 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 usage context: it gathers raw material for the daily insight and instructs users to read the stored result later with get_daily_insight. However, it does not explicitly state when not to use this tool or mention alternative approaches, leaving some room for ambiguity.

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_PH'

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