Skip to main content
Glama

RICE Priority Score

bpj_rice_priority
Read-onlyIdempotent

Calculate a comparable RICE score using reach, impact, confidence and person-months of effort.

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": {
      "reach": "<reach>",
      "impact": "<impact>",
      "confidence": "<confidence>",
      "effort": "<effort>"
    },
    "name": "bpj_rice_priority"
  }
}

Input Schema

NameRequiredDescriptionDefault
reachYes
effortYes
impactYes
confidenceYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety and determinism profile is fully covered by structured data. The description adds only the word 'comparable', hinting at normalized output, and restates effort units already in the schema title. It does not disclose the scoring formula or output shape.

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

Conciseness5/5

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

A single front-loaded sentence with zero filler that maps directly onto the four required inputs. Nothing is buried or redundant.

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?

For a four-parameter pure calculator with no output schema, the definition is adequate but thin: it never states the RICE formula (reach × impact × confidence / effort) or that the result is a single number, which is the main thing an agent might need to interpret the return value. The annotation set does cover the safety profile, so the remaining gap is moderate rather than severe.

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

Parameters3/5

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

Schema description coverage is 0%, but each property carries a descriptive title (Reach in the same period, Impact multiplier 0–3, Confidence %, Effort in person-months). The description names all four parameters and repeats the person-months unit for effort, but adds no formula relationship or worked semantics beyond the titles.

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 uses a specific verb ('Calculate') with a named resource ('comparable RICE score') and enumerates the four inputs, so the tool's function is immediately clear. It does not differentiate itself from any sibling, but no sibling appears to compute RICE, so the ambiguity cost is low.

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 use this tool versus alternatives, no prerequisites, and no statement of constraints such as whether inputs must be positive or how ties are handled. The agent must infer that this is used for backlog prioritization purely from the RICE name.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.