Skip to main content
Glama

Ragmir audit: Ragmir

ragmir_audit
Read-onlyIdempotent

Audit source coverage against the search index to detect missing, stale, or uncovered files, ineffective source rules, and index concentration when search results look incomplete.

Instructions

Diagnose the "Ragmir" sources rather than search them: compare files on disk with the index for coverage, missing or stale files, source rules that match nothing, and index concentration. Use it when results look incomplete; ragmir_status is the quicker readiness check. Returns a summary unless detail:true.

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

Input Schema

NameRequiredDescriptionDefault
detailNotrue lists every affected path instead of counts and the first examples.
maxBytesNoOutput budget in bytes for this call; the server caps it at its configured maximum.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv6.15.0
    • addedInput schema / properties / detail / description
      Added value: +"true lists every affected path instead of counts and the first examples."
    • addedInput schema / properties / maxBytes / description
      Added value: +"Output budget in bytes for this call; the server caps it at its configured maximum."
  2. First observedv0.1.0

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, and closed-world, so the safety profile is covered. The description adds genuinely new behavioral information: the default response is a summary, and detail:true switches to per-path listings. It does not discuss cost, latency, or the effect of the output budget, which keeps it below a 5.

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?

Two sentences, front-loaded with the core distinction from search, then the usage rule, then the return behavior. No filler or redundant restatement of the title.

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?

There is no output schema, but the description compensates by stating what the call returns and how detail changes it, and it names the sibling that covers the lighter-weight case. For a two-parameter, side-effect-free diagnostic tool, an agent has everything needed to call it correctly.

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 both parameters are already documented in the schema, including detail's exact effect and maxBytes' server cap. The description only restates the detail behavior, adding minimal meaning beyond the schema; 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 ("Diagnose") and resource (the Ragmir sources), then enumerates the concrete checks: coverage, missing or stale files, source rules that match nothing, and index concentration. It also explicitly contrasts itself with searching and names the sibling ragmir_status, so an agent can distinguish it without opening another 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 the triggering condition ("Use it when results look incomplete") and gives the alternative plus its selection rule ("ragmir_status is the quicker readiness check"). That is explicit when-to-use and when-to-use-something-else guidance.

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