Skip to main content
Glama

Metis — Capture Idea

capture_idea

Store an idea and automatically extract tags, link to related domains or projects, and discover cross-pollination connections from your library, meetings, and news.

Instructions

Store an idea in the SQLite ideas table.

Auto-extracts tags from content. Links to domains/projects if keywords match.
Unless `auto_cross_pollinate=False`, automatically surfaces up to 5 cross-
pollination matches from library / meetings / news / older ideas in the same
response — so the user sees connections without a second tool call.

Args:
    content: The idea text.
    source: Where the idea came from (default "manual").
    image_path: Optional path to an associated image.
    auto_cross_pollinate: When True (default), include connection matches in the response.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
sourceNomanual
contentYes
image_pathNo
auto_cross_pollinateNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior4/5

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

No annotations, so description bears full burden. It discloses auto-tag extraction, domain/project linking, and cross-pollination behavior. Could mention if other tables are modified, but overall adequate.

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?

Concise, front-loaded with main action, and uses an Args section. Every sentence adds value without redundancy.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With output schema present, return values need not be described. Covers core functionality, side effects, and parameter details. Could mention content length constraints but not critical.

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%, but description adds meaningful context for all 4 parameters: content as idea text, source with default, image_path optional, and auto_cross_pollinate with behavior explanation. Fully compensates for schema gaps.

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?

Description clearly states 'Store an idea in the SQLite ideas table' with specific verb and resource. Distinguishes from siblings like add_memory_entry and capture_observation by mentioning auto-tagging and cross-pollination.

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

Usage Guidelines3/5

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

Implies usage for capturing ideas with automatic connections, but no explicit when-not-to-use or alternatives. The cross-pollination feature is highlighted, but no guidance on when to disable it.

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