Skip to main content
Glama

BRAINIAC Staking Operations

Audit staking reward allocation

staking-operations_staking-reward-allocation-audit
Read-onlyIdempotent

Calculate staking reward allocations from the supplied commission percent, share percents, penalties, and rounding rule. Share percents must sum to 100%. Commission is that percent of gross rewards or of rewards after penalties. audit_status is balanced, mismatched, invalid, or incomplete. Expected amounts are calculated. Actual amounts come only from distribution records in the request. No staking reward is fetched, and this is not an invoice or stablecoin reconciliation. Price $0.05 USDC. POST /api/v1/staking-operations/staking-reward-allocation-audit. 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": {
      "periods": "<periods>"
    },
    "name": "staking-operations_staking-reward-allocation-audit"
  }
}

Input Schema

NameRequiredDescriptionDefault
periodsYesperiods, array. Required.
distributionsNodistributions, array. Optional.

Output Schema

NameRequiredDescriptionDefault
findingsNofindings. Array.
limitationsNolimitations. Array.
audit_statusNoaudit_status. String.
total_rewardsNototal_rewards. String.
total_allocatedNototal_allocated. String.
operator_allocationsNooperator_allocations. Array.
delegator_allocationsNodelegator_allocations. Array.
undistributed_rewardsNoundistributed_rewards. String.
commission_differencesNocommission_differences. Array.
distribution_mismatchesNodistribution_mismatches. Array.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior5/5

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

Beyond the readOnly/idempotent/non-destructive annotations, it discloses pricing ($0.05 USDC), the transport (POST /api/v1/staking-operations/staking-reward-allocation-audit), and crucially that an unpaid call returns x402 payment terms without executing. It also states the computation is deterministic from supplied data and that actual amounts come only from distribution records in the request, which is behavior an agent cannot infer from annotations.

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?

Content is front-loaded with the purpose, then constraints, then output semantics, then cost and transport — a sensible order with little waste. The middle section is telegraphic ('Expected amounts are calculated. Actual amounts come only from distribution records') and reads as compressed notes rather than flowing prose, which slightly hurts scanability but not correctness.

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?

For a two-parameter tool whose payload is a deeply nested periods array, the description covers the semantics that matter: the sum-to-100 rule, commission basis, the four audit_status outcomes, and the expected-vs-actual split. Since an output schema exists, it correctly does not re-describe return values. The only gap is no guidance on the remainder or rounding policies beyond restating the schema enums.

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

Parameters4/5

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

Schema coverage is 100%, so the baseline is 3, but the description adds real semantic meaning: the 100% sum constraint on shares, the two commission bases ('percent of gross rewards or of rewards after penalties'), and the distinction between computed expected amounts and request-supplied actuals. It stops short of explaining individual fields like remainder or statedCommission, which the schema names but does not fully disambiguate.

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

Purpose5/5

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

The description opens with a specific verb and resource ('Calculate staking reward allocations') and immediately enumerates the inputs it consumes (commission percent, share percents, penalties, rounding rule). It further fences the scope negatively with 'No staking reward is fetched' and 'this is not an invoice or stablecoin reconciliation', which lets an agent distinguish it from the reward-fairness sibling without opening either schema.

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

Usage Guidelines4/5

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

It gives a clear precondition ('Share percents must sum to 100%') and explicit exclusions (not invoice or stablecoin reconciliation, does not fetch rewards). What it lacks is a positive routing statement telling the agent when to pick this versus staking-operations_reward-fairness, so the alternative is implied rather than named.

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