Skip to main content
Glama
SVerITG

Metis

by SVerITG
OverviewSchemaRelated ServersScoreDiscussions
Python
Local

Metis · News Radar — Save Daily Brief

save_daily_brief

Save a composed daily brief to the database for display on the dashboard widget.

Instructions

Save a composed daily brief so the dashboard widget shows it.

This is the write-back half of the daily-brief round-trip. Claude Desktop (or
Claude Code) composes the brief from generate_daily_insight() context, then
calls this to upsert the finished prose into the daily_insights table — the
same table the dashboard's morning-brief widget reads via get_daily_insight().
Desktop and the dashboard share one database, so no files are involved: once
saved, the brief appears in the dashboard on next load.

Args:
    content: The finished daily-brief prose (markdown ok). Required.
    sources: Comma-separated list of what the brief drew on (optional).
    date: YYYY-MM-DD; empty = today.
    model: Model identifier that composed it, for provenance (optional).

Returns:
    Confirmation with the date saved and a pointer to the dashboard widget.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
dateNo
modelNodesktop-brief
contentYes
sourcesNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Tool Definition Quality

A4.5/5.0
Behavior4/5

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

With no annotations provided, the description carries the full burden. It explicitly states this is a write operation (upsert), mentions that it affects the dashboard widget on next load, and notes that desktop and dashboard share a database. No contradictions with annotations since none exist.

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 well-structured with a clear top-level purpose, followed by contextual detail, and then a labeled Args section. It is concise but includes essential details. Minor improvement could be made by slightly tightening the prose, but overall it's effective and earns its length.

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 complexity (4 parameters, no annotations, but an output schema described in the Returns note), the description covers all necessary aspects: purpose, usage flow, parameter meanings, and return value. It references sibling tools (generate_daily_insight, get_daily_insight) and explains the shared database context, making it complete for agent decision-making.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The description includes an Args section that adds meaning to all 4 parameters: content is 'finished daily-brief prose', sources is 'comma-separated list', date is 'YYYY-MM-DD', model is 'for provenance'. The schema itself has no descriptions (coverage 0%), so the description fully compensates and provides clear semantics.

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 saves a composed daily brief to the dashboard widget. It distinguishes itself as the write-back half of the daily-brief round-trip, contrasting with generate_daily_insight() and get_daily_insight(). The verb 'save' combined with the resource 'daily brief' is specific and unambiguous.

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?

It explains that this tool is used after composing the brief from generate_daily_insight() context, and that it upserts into the same table the dashboard reads. This provides clear when-to-use guidance. However, it does not explicitly state when not to use it or list alternative tools beyond the sibling get_daily_insight.

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