Metis

Overview Schema Source Related Servers Discussions Admin

Metis — Get Ideas

get_ideas

Retrieve captured ideas from your knowledge base newest first by time window, helping you review recent thoughts and decide what to revisit, connect, or act on.

Instructions

List captured ideas from your knowledge base, newest first.

Use this to review what you've been thinking about over a chosen time
window — the ideas you logged with capture_idea — so you can revisit,
connect, or act on them. Pairs with capture_idea (to add) and
cross_pollinate (to surface related work).

Args:
    scope: Time window to retrieve. One of "today", "week" (last 7 days),
        "month" (last 30 days), or "all". Defaults to "week".
    limit: Maximum number of ideas to return, newest first. Defaults to 20.

Returns:
    A formatted list of matching ideas with their timestamps and tags, or a
    friendly note if none were found in that window.

Input Schema

Name	Required	Description	Default
`limit`	No
`scope`	No		week

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Jun 8, 2026

TDQS

A4.8/5.0

Behavior4/5

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

No annotations provided, so description carries full burden. It discloses ordering (newest first), default parameters, and return format ('formatted list' or 'friendly note'). Minor gap: doesn't specify pagination limits beyond limit parameter, but adequate for simple read operation.

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: one sentence for purpose, one for usage context, then structured Args and Returns sections. Every sentence adds value, with no repetition or fluff.

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, the description covers everything an agent needs: purpose, parameters, expected output, and usage context. It references sibling tools and explains the scope options, making it self-contained.

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 coverage is 0% (no parameter descriptions in schema), but description compensates fully. It explains scope enum values with defaults and limit max, adding essential meaning beyond the raw 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 action ('List captured ideas') and resource ('from your knowledge base, newest first'). It distinguishes itself from sibling tools by naming capture_idea and cross_pollinate, which are nearby in the sibling list.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly states when to use: 'review what you've been thinking about over a chosen time window.' Provides context: 'ideas you logged with capture_idea.' Mentions sibling tools for adding and connecting, giving clear alternatives.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server