Skip to main content
Glama

Rgi Explain

rgi_explain

Explains the confidence and factors behind a decision by decision ID, helping users understand why a scoring outcome occurred.

Instructions

Explain the confidence and factors behind a decision.

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

Input Schema

NameRequiredDescriptionDefault
decision_idNolast

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.7/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, yet it says nothing about whether this is a safe read, what happens for an unknown or missing decision id, or how the default 'last' is resolved. It does hint at the conceptual response (confidence and factors), but the output schema already covers return structure.

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?

A single front-loaded sentence with no filler, which is structurally clean. However, its brevity is under-specification rather than efficiency, since key calling details are omitted.

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?

An output schema exists, so return values need not be spelled out here, which limits the required scope. Still, for a tool with an ambiguous default parameter and no annotations, the description leaves the agent guessing about default resolution and error behavior.

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 decision_id has 0% schema description coverage, so the description must compensate and does not. It never mentions decision_id, the meaning of the default value 'last', or accepted id formats, leaving the caller unable to know what to pass.

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 a specific verb (explain) and object (a decision), and adds what the explanation contains: confidence and contributing factors. That is enough to distinguish it from siblings like rgi_score or rgi_verify, though it does not explicitly name an alternative.

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 guidance on when to call this versus rgi_decisions, rgi_verify, or rgi_score, and no preconditions such as whether a decision must already exist. The use case is only implied by the word 'explain'.

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