Skip to main content
Glama

Rgi Conservation

rgi_conservation

Reports Judgment Memory conservation health, helping you detect degradation and maintain decision quality.

Instructions

Report Judgment Memory conservation 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": "rgi_conservation"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.8/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full behavioral burden, and it discloses almost nothing: "Report" weakly implies a read-only operation, but there is no statement of what health means, what is measured, whether it mutates state, or any cost/latency characteristics. The presence of an output schema covers return values, but not the operation's semantics.

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 short sentence with no wasted words and the verb front-loaded. It is efficient, though its brevity shades into under-specification rather than genuine crispness.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a zero-parameter tool with an output schema, the description still needs to say what "conservation health" denotes and when an agent should call it. Neither is present, and no differentiation from the five sibling rgi_* tools is given.

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 the baseline is 4; there is no parameter semantics for the description to explain. No penalty applies for the absence of parameter detail.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

"Report ... conservation health" gives a verb and a resource, but the resource is undefined jargon ("Judgment Memory conservation health") that an agent cannot map to a concrete result. Nothing distinguishes it from siblings such as rgi_accuracy or rgi_score, which plausibly report related health-like signals.

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?

The description offers no when-to-use guidance, no conditions, and no reference to any of the sibling tools. An agent has no stated basis for choosing this over rgi_accuracy or rgi_score.

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