Skip to main content
Glama

obit_stats

Read-only

Reports tracked items, graveyard size, lifetime counters, and delete guard counts so you can monitor file expiry and burial activity.

Instructions

Reports tracked items, graveyard size, lifetime counters and delete guard counts.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and idempotentHint=false, so the safety profile is covered; the description's contribution is telling the agent what categories of data come back, which is useful context beyond the annotations. However it does not explain the non-idempotent implication (counters drift as items are buried/resurrected) or whether 'delete guard counts' reflects currently-blocked deletes — behavioral gaps that matter for interpreting a snapshot.

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?

A single front-loaded sentence with no filler or repetition; the four reported categories are packed efficiently into one list. It is tight but trades away some interpretability for compactness.

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?

With no output schema and no parameters, the description is the only source of return-value information, and it only names category labels without structure, units, or shape. Terms like 'delete guard counts' and 'lifetime counters' are domain jargon an agent cannot resolve from the definition alone, so it is adequate but thin for a tool whose entire value is its return data.

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 zero parameters, so there is no parameter meaning to add; the baseline for a no-arg tool applies. Nothing in the description misrepresents the input surface, which the schema confirms is an empty object.

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?

States a specific verb ('Reports') and enumerates the resource categories returned: tracked items, graveyard size, lifetime counters, delete guard counts. That is far more informative than a restatement of the name, though it never names a sibling to contrast with obit_list or obit_graveyard, both of which plausibly also surface tracked/graveyard data.

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?

There is no when-to-use guidance at all — nothing tells the agent to call this for an overview before choosing among obit_list, obit_graveyard, or obit_proposals, nor any prerequisite or cost note. Usage can only be inferred from the word 'stats'.

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