Skip to main content
Glama

Rgi Score

rgi_score

Score a decision using a category and weighted factors, returning action probabilities to guide next steps.

Instructions

Score a decision and return action probabilities.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "category": "<category>",
      "factors": "<factors>"
    },
    "name": "rgi_score"
  }
}

Input Schema

NameRequiredDescriptionDefault
factorsYes
categoryYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.2/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 does very little with it. It states that action probabilities are returned, but says nothing about whether this is a pure computation or has side effects, whether results are deterministic, what the inputs must contain, or how 'factors' influence the result. With an output schema present, the return-value gap is forgiven, but the operational characteristics are not.

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?

It is a single front-loaded sentence with zero filler, which satisfies the structural test. The terseness is under-specification rather than concision, so it earns only a middling score despite containing no wasted words.

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 tool with a nested free-form parameter object, no annotations, and 0% schema coverage, the description is far too thin to be callable with confidence. The output schema covers the return shape, but the input contract and the relationship to five sibling tools remain undocumented.

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% and the description adds no meaning to either parameter. 'factors' is a free-form object of arbitrary numeric properties and 'category' is an unconstrained string, so the description needed to explain accepted keys, value ranges, and accepted category values; it explains nothing.

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 gives a verb ('Score') and an object ('a decision') plus a return hint ('action probabilities'), which is more than a restatement of the name. However, 'score' and 'decision' are undefined domain terms (the RGI acronym is never expanded), and nothing distinguishes this from sibling tools like rgi_accuracy or rgi_verify. An agent cannot confidently tell what scoring a decision actually entails.

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 prerequisites, and no mention of the sibling tools (rgi_accuracy, rgi_conservation, rgi_decisions, rgi_explain, rgi_verify) whose names suggest overlapping purposes. The agent must infer the selection criteria entirely from names it cannot see in the definition itself.

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