Skip to main content
Glama

Ragmir ingest: Ragmir

ragmir_ingest
Idempotent

Refresh the Ragmir knowledge base after source files change by re-reading only new or modified files, keeping the previous index searchable until validation, and writing only Ragmir's private index.

Instructions

Refresh the "Ragmir" knowledge base after its source files changed: an incremental ingest that re-reads only new or modified files and keeps the previous index searchable until the new one is validated. It writes only Ragmir's private index, never project files. Call it when ragmir_status, ragmir_sources, or search results report missing or changed files. It waits up to waitSeconds (default 30) and reports progress when the run takes longer; call it again to keep waiting. Which files are indexed is set in the project's Ragmir configuration, not here.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "ragmir_ingest"
  }
}

Input Schema

NameRequiredDescriptionDefault
waitSecondsNoSeconds to wait for the run to finish, 0 to 600. Default 30; the run continues in the background afterwards.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv6.15.0

TDQS

A4.8/5.0
Behavior5/5

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

Beyond the annotations (readOnlyHint=false, idempotent, non-destructive), it discloses what is written ('only Ragmir's private index, never project files'), that the prior index stays searchable until validation, that the run continues in the background after the wait, and that progress is reported — all non-obvious operational facts.

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

Conciseness4/5

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

It is a single dense paragraph but front-loaded with the action, then safety, then trigger, then parameter behavior; each sentence carries distinct information, though the density makes it slightly harder to scan.

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?

For a one-parameter mutation with no output schema, the description covers trigger conditions, write scope, index availability during the run, wait/continuation semantics, and the boundary that file selection lives in project configuration — nothing needed to call it correctly is missing.

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?

Schema coverage is 100% and documents waitSeconds with its 0-600 range and default, so the baseline is 3; the description adds the non-schema behavior that the run keeps going in the background and that a second call continues waiting, adding real meaning.

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 states a specific verb and resource ('Refresh the Ragmir knowledge base') and immediately qualifies it as 'an incremental ingest that re-reads only new or modified files,' which an agent can distinguish from sibling reads like ragmir_status or ragmir_search.

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?

It gives an explicit trigger ('Call it when ragmir_status, ragmir_sources, or search results report missing or changed files') and an explicit follow-up rule ('call it again to keep waiting'), so the when and the repeat condition are both stated.

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