Skip to main content
Glama

Ragmir sources: Ragmir

ragmir_sources
Read-onlyIdempotent

Lists indexed documents with chunk counts and shows files missing from or changed since indexing. Use it to choose includePaths for ragmir_search.

Instructions

List the documents of the "Ragmir" knowledge base (/app): indexed files with their chunk counts, and files missing from the index or changed since indexing. Filter with paths (folders, files, or globs such as docs/** or **/*.pdf) and page with offset. Use it to answer which documents exist or to choose includePaths for ragmir_search; ragmir_search finds what they say. Read-only.

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_sources"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoFiles per page, 1 to 100. Default 50.
pathsNoFolders, files, or globs such as docs/** or **/*.pdf. Lists every indexed file when omitted.
offsetNoFiles to skip; pass page.nextOffset from the previous call to read the next page.
maxBytesNoOutput budget in bytes for this call; the server caps it at its configured maximum.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv6.15.0

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive and closed-world, so the closing "Read-only." adds nothing. What the description does add is substantive: with no output schema, it discloses the three result categories (indexed with chunk counts, missing from index, changed since indexing), which tells the agent what a call will actually yield. Ordering, auth, and rate-limit behavior remain unstated.

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?

The core capability and the filter/paging mechanics are front-loaded and there is no filler. The final "Read-only." duplicates the annotations, and the middle of the description is dense enough to approach run-on, but overall it is efficient.

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?

For a paged, filtered listing tool with full schema coverage and no output schema, the description covers what is returned, how to filter, and how to page. It does not say how results are ordered or whether the missing/changed lists are bounded, which would matter when deciding how many pages to read.

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 description coverage is 100%, so all four parameters are already documented, including glob examples and the nextOffset paging convention. The description restates globs ("docs/** or **/*.pdf") and offset paging but adds no semantics the schema lacks, so the baseline 3 applies.

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 names a specific verb and resource ("List the documents of the 'Ragmir' knowledge base") and enumerates exactly what is returned: indexed files with chunk counts plus files missing from the index or changed since indexing. It explicitly separates itself from ragmir_search ("ragmir_search finds what they say"), so an agent can choose between them without opening either schema.

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 states concrete use cases ("answer which documents exist or to choose includePaths for ragmir_search") and names the alternative tool with the condition that selects it. The boundary between inventory work and content search is spelled out rather than left to inference.

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