Skip to main content
Glama

Rgi Decisions

rgi_decisions

Fetch recent Judgment Memory decisions to review prior scoring outcomes and inform recursive graph improvement.

Instructions

Return recent Judgment Memory decisions.

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

Input Schema

NameRequiredDescriptionDefault
limitNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.4/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 burden, yet it only implies a read. "Recent" is undefined (no time window, no ordering), and there is no statement about pagination, whether results are truncated, or whether any auth scope is required.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The one-sentence form is efficient with no wasted words, but here brevity shades into under-specification rather than conciseness. There is no structure beyond a single clause.

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?

An output schema exists, so return values needn't be explained, but for a retrieval tool with no annotations the description should still pin down the recency window and the meaning of limit. Neither is covered, leaving the definition materially incomplete.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The single parameter, limit, has 0% schema description coverage and is not mentioned in the description at all, so the agent must guess whether it caps results, controls recency, or something else. Only the schema's type and default of 10 provide any grounding.

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?

The description pairs the verb "Return" with a specific resource, "recent Judgment Memory decisions," which is more than a tautology of the name. However, "Judgment Memory" is domain jargon and "decisions" is never defined, so an agent cannot form a precise picture of what is returned or how it differs from siblings like rgi_score or rgi_explain.

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, no exclusions, and no mention of when a sibling such as rgi_explain or rgi_verify would be preferable. The agent is left to infer entirely from the tool name that this is a retrieval operation.

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