Skip to main content
Glama

ingest_data

Ingest text, Markdown, or HTML content into minirag-mcp under a stable source ID; reuse the same ID to update or replace previously indexed content.

Instructions

Ingest text/markdown/html content the client holds, under a source id you choose.

format is one of "text", "markdown", or "html" (default "text"). source is a stable identifier you pick, not a filesystem path — re-using it replaces the previously ingested content for that id, so reuse the same source to update an item. labelProblem is as in ingest_file.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "data": "<data>",
      "source": "<source>"
    },
    "name": "ingest_data"
  }
}

Input Schema

NameRequiredDescriptionDefault
dataYes
titleNo
formatNotext
sourceYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.3/5.0
Behavior3/5

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

With no annotations, the description carries the full burden, and it does disclose the key behavioral trait: re-using a source replaces prior content, so this is a mutating operation with overwrite semantics. It omits permissions/auth requirements, and the `labelProblem` reference describes behavior that has no corresponding parameter here, which muddies rather than clarifies.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The core is front-loaded and compact, with the source-id rule stated efficiently. The trailing '`labelProblem` is as in ingest_file' sentence is dead weight for this schema and forces the reader to resolve a reference that does not apply.

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?

An output schema exists, so return values need not be explained, and the overwrite semantics are covered. Still, with four parameters at 0% schema coverage, one parameter (`title`) is left entirely undocumented, and the definition never routes the agent between this tool and the file/URL ingest siblings.

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

Parameters3/5

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

Schema coverage is 0%, so the description must compensate, and it does add real meaning for format (enumerated values plus default) and source (a chosen stable id, not a filesystem path, with replace-on-reuse semantics). But `title` is never mentioned, and `labelProblem` is described as though it were a parameter when it is not in the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb (ingest) and resource (text/markdown/html content the client already holds), and the phrase 'the client holds' implicitly contrasts with the file- and URL-based siblings. It does not name ingest_file or ingest_url as alternatives, so the differentiation is inferential rather than explicit.

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?

It gives a genuine usage rule — reuse the same source id to update an item rather than creating a new one — which is real when-to guidance. However it never states when to pick this tool over ingest_file or ingest_url, and the closing reference to `labelProblem` points at something outside this tool's schema.

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