Skip to main content
Glama

save_daily_brief

Save a composed daily brief to the database, immediately updating the dashboard widget. Returns confirmation with date and model provenance.

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
contentYes
sourcesNo
dateNo
modelNodesktop-brief

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 the upsert behavior, target table, and that no files are involved, providing sufficient behavioral transparency for a write operation.

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 summary, explanatory paragraph, and Args list, front-loading the main purpose. Slightly verbose but every sentence is meaningful.

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 and the presence of an output schema, the description completely covers the workflow, parameters, and return values, leaving no gaps for the agent to interpret.

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?

Schema description coverage is 0%, but the description provides detailed parameter semantics: content as required markdown, sources as comma-separated, date format with empty=default, and model default, adding significant value beyond the schema.

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 saves a composed daily brief for the dashboard widget, and explicitly distinguishes it from the complementary tools generate_daily_insight and get_daily_insight, providing specific verb+resource+scope.

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 explains the tool is the write-back half of a round-trip, after generating the brief with generate_daily_insight, and before reading with get_daily_insight, giving clear context on when to use it, though it lacks explicit when-not scenarios or alternatives.

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