Skip to main content
Glama

Metis — Ingest Ideas Document

ingest_ideas_document

Import a document containing ideas, then split it into discrete items and capture each one automatically.

Instructions

Import an ideas document (Word/text/markdown) and capture each idea.

Reads the file, splits it into discrete items (paragraphs, bullet points,
or numbered items), and calls capture_idea() for each non-empty item.
Supports .txt, .md, and .docx files.

Args:
    file_path: Absolute or METIS_RC_ROOT-relative path to the ideas file.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
file_pathYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior3/5

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

The description explains the reading, splitting, and calling of capture_idea() per item. It does not mention error handling, duplicate detection, or limits. No annotations are present to supplement, so it carries the full burden but is 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?

The description is concise: three sentences plus a single bullet for the argument. It is front-loaded with the purpose, and every sentence adds value with no redundancy.

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

Completeness3/5

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

Given the output schema exists (assumed to document return values), the description covers input, process, and file types adequately. It lacks details on edge cases like empty files or duplicates, but is sufficient for a simple tool.

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

Parameters4/5

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

The only parameter, file_path, is described as absolute or relative to METIS_RC_ROOT. This adds meaning beyond the schema property name. Since schema description coverage is 0%, the description compensates well.

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 imports an ideas document and captures each idea by splitting into discrete items and calling capture_idea(). It specifies supported file formats (.txt, .md, .docx). This distinguishes it from the sibling tool capture_idea which handles single ideas.

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?

The description implies usage for bulk import of ideas from a document, but does not explicitly state when to use this tool versus capture_idea for individual entries. No exclusion or alternative guidance is provided.

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