Skip to main content
Glama

save_review

Persist agent output as a markdown review file and log the run for dashboard tracking. Use it to file and discover completed tasks.

Instructions

Save an agent's output as a review file and record the run.

This is the standard way a Metis agent persists its work: it writes the
markdown to outputs/reviews/{agent_slug}/{date}_{task_slug}.md and, by
default, logs the run so the dashboard's Agents tab tracks it. Use it at the
end of any substantive agent task so the result is filed and discoverable.

Args:
    agent_slug: Slug of the agent that produced the review
        (e.g. "epidemiologist", "writing-partner").
    task_slug: Short kebab-case slug identifying the task; becomes part of
        the filename (e.g. "article1-methodology").
    content: The full review content as markdown.
    log_run: Whether to also record this as an agent run for the dashboard.
        Defaults to True.

Returns:
    A confirmation with the path of the saved review file.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
agent_slugYes
task_slugYes
contentYes
log_runNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior5/5

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

With no annotations, description fully discloses file path structure, default logging behavior, and dashboard tracking. No contradictions.

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?

Front-loaded with action; structured with summary, context, Args, Returns. Every sentence adds value without redundancy.

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?

Explains return value, use case, and parameter details comprehensively. Output schema exists to further document return structure.

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 has 0% description coverage; description adds detailed explanations for all 4 parameters with examples and defaults, greatly surpassing schema titles.

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?

Clear verb 'save' with specific resource 'review file' and action 'record the run'. Distinguishes from siblings like save_brainstorm_output by specifying it's for agent output reviews.

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?

Explicitly states to use at end of substantive agent tasks. Provides context for discoverability but no direct exclusions or alternatives mentioned.

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