Skip to main content
Glama

BRAINIAC Staking Operations

Score staking reward fairness

staking-operations_reward-fairness
Read-onlyIdempotent

Compare each supplied allocation with the share of the reward pool its weight implies. The rounding error is the total absolute gap, divided by the reward. Equal weights with uneven payouts lower the fairness score. No reward balance is fetched. Price $0.04 USDC. POST /api/v1/staking-operations/reward-fairness. An unpaid call returns the x402 payment terms and does not run.

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": {
      "reward": "<reward>",
      "shares": "<shares>"
    },
    "name": "staking-operations_reward-fairness"
  }
}

Input Schema

NameRequiredDescriptionDefault
rewardYesreward, integer, from any to 9007199254740991. Required.
sharesYesshares, array. Required.

Output Schema

NameRequiredDescriptionDefault
allocation_fairness_scoreNoallocation_fairness_score. Number.
rounding_error_percentageNorounding_error_percentage. Number.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

The annotations already state readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so the safety profile needs no further explanation. The description adds behavior the annotations do not cover: it does not fetch reward balances, it costs $0.04 USDC, it uses POST to a specific endpoint, and an unpaid call returns x402 payment terms without running. That is meaningful context beyond the structured fields.

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

Conciseness4/5

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

The description leads with the core computation, then gives the metric definition, the score behavior, the scope constraint and the pricing and transport details. Every sentence carries information, though the terse endpoint and price line reads more like boilerplate than the rest.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

An output schema exists, so the description need not explain the shape of the returned values, and for a two-parameter read-only scoring computation it covers inputs, method and payment behavior. It leaves the numeric range of the fairness score implicit, relying on the output schema to supply it.

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 100% and the schema already documents reward, shares, id, weight and allocated with their bounds. The description explains the semantics of weight against allocated, says that rounding error is total absolute gap divided by reward, and notes that equal weights with uneven payouts lower the score. That adds interpretive meaning, so it is at the baseline for fully documented schemas rather than above it.

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 states a specific verb and resource: it compares each supplied allocation against the share implied by its weight, and it names the fairness score and rounding error as its outputs. It does not explicitly distinguish itself from the sibling allocation-audit tool, so it stops short of a 5.

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

Usage Guidelines3/5

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

The description implies usage through the computation it performs and the note that 'No reward balance is fetched', which sets its scope. It never states when to choose this tool over staking-operations_staking-reward-allocation-audit or what inputs are prerequisites, so the guidance is implied rather than explicit.

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.

Resources