Skip to main content
Glama

Ragmir status: Ragmir

ragmir_status
Read-onlyIdempotent

Check whether the Ragmir knowledge base is ready to search, verify index freshness, embedding model, and available scopes, then get next steps if indexing status is unclear.

Instructions

Quick health check of the "Ragmir" knowledge base (/app): whether it is ready to search, index freshness, the embedding model, the named scopes ragmir_search accepts, and next steps. Call it first when unsure the base is indexed; use ragmir_audit to find which files are missing or stale.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and a closed world, so safety is covered structurally. The description adds useful behavior beyond that: the response reveals scopes that ragmir_search accepts, which makes the tool double as discovery for a sibling. It stops short of saying how large/slow the check is or whether it hits disk vs. cached state, which keeps it off 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 purpose and the enumeration of returned facts, then the routing rule. No filler or restatement of the title; every clause carries information an agent would otherwise have to discover by calling.

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?

No output schema exists, but the description compensates by listing the concrete facts returned (readiness, freshness, model, scopes, next steps). For a zero-parameter read-only status tool, nothing an agent needs in order to decide to call it 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?

Zero parameters, so there is no parameter meaning to convey and the empty schema is self-explanatory. Baseline for a parameterless tool.

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?

States a specific verb+resource ('Quick health check of the "Ragmir" knowledge base') and then enumerates exactly what the check covers: readiness to search, index freshness, embedding model, accepted scopes, next steps. The sibling ragmir_audit is named as the different, file-level tool, so an agent can separate the two without opening a 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?

Gives an explicit trigger ('Call it first when unsure the base is indexed') and an explicit alternative ('use ragmir_audit to find which files are missing or stale'). The selection condition between the two tools is stated, not inferred.

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