Skip to main content
Glama

Rgi Verify

rgi_verify

Record whether a stored decision was correct so the graph attention engine can learn from the outcome and refine future decision scoring.

Instructions

Learn from a verified decision outcome.

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

Input Schema

NameRequiredDescriptionDefault
correctNo
gt_actionNo
decision_idNolast

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

D1.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 disclosure burden and largely fails it. "Learn from" vaguely implies persistent state change or model updating, but the description never states whether the call mutates stored knowledge, whether it is reversible or idempotent, what permissions it needs, or what happens with the default decision_id="last".

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 single sentence contains no filler or redundancy, so nothing is wasted. However, brevity here reflects under-specification rather than economy: the sentence is too thin to orient an agent before invocation.

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 need not be explained. But for a three-parameter tool with zero schema documentation and no annotations, the description supplies none of the operational context (preconditions, side effects, parameter meaning) an agent needs to invoke it correctly.

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

Parameters1/5

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

Schema description coverage is 0% for all three parameters (correct, gt_action, decision_id), and the description adds no meaning to any of them. An agent cannot tell that 'correct' is a feedback flag defaulting to true, that 'gt_action' is the ground-truth action, or that 'decision_id' defaults to the last decision.

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

Purpose2/5

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

"Learn from a verified decision outcome" restates the tool name (rgi_verify) without naming a concrete action or resource. It does not clarify whether the tool records feedback, updates a model, or scores a decision, and gives no basis for distinguishing it from siblings such as rgi_score or rgi_accuracy.

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

Usage Guidelines1/5

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

There is no statement of when to call this tool, what precondition (e.g., a completed decision or a ground-truth label) is required, or which sibling to use instead. The only hint is the phrase "verified decision outcome," which an agent cannot act on reliably.

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