Skip to main content
Glama

status

Check index statistics—documents, chunks, mentions—and Ollama backend health to verify your local semantic search and recall system is operational.

Instructions

Index stats (documents/chunks/mentions) and Ollama backend health.

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": "status"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.0.0

TDQS

B3.4/5.0
Behavior3/5

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

With no annotations, the description must carry the behavioral burden, and it does disclose the two output areas and implies a read-only diagnostic that probes an external service (Ollama), which hints at a possible network dependency or latency. It does not say whether an unreachable backend raises an error or is reported in the payload, nor whether the call is cheap enough to poll.

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?

A single front-loaded sentence with no filler; every element (index stats, the three counted entities, backend health) carries information. Nothing could be cut without losing content.

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?

For a zero-arg diagnostic with no output schema, the description should sketch the returned shape, and it does list the stat categories, but it says nothing about failure modes or whether the health probe is live. Adequate for a simple status tool, not fully complete.

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?

The tool takes no parameters, so there is no parameter semantics to explain and the schema leaves nothing ambiguous. Baseline 4 applies for a zero-argument tool.

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?

The description names the concrete resources reported — index statistics broken down by documents, chunks, and mentions, plus Ollama backend health. That is enough to separate it from the memory/learning siblings listed. It lacks an explicit verb ("reports" / "returns"), which keeps it from a 5.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Nothing states when to call this versus other tools, whether it should be used before writes to confirm backend availability, or whether it requires any prerequisites. The only guidance is implicit in the word "status" and the mention of health.

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