Skip to main content
Glama

BRAINIAC Staking Security

Audit validator slashing protection

staking-security_validator-slashing-protection-audit
Read-onlyIdempotent

Check caller-supplied EIP-3076 version 5 slashing-protection interchanges before validator history is imported or reused. A double proposal is two different blocks at the same slot. A double vote is two different attestations with the same target epoch. A surround vote has an earlier source epoch and a later target epoch than the vote it surrounds. audit_status is safe, conflicts_detected, warnings, invalid, or incomplete. risk_level is low, medium, high, or critical. Identical records without signing_root are not a confirmed slash. The export is not a complete signing history and does not protect against a later signature. No private key is accepted and no beacon node is queried. Price $0.05 USDC. POST /api/v1/staking-security/validator-slashing-protection-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": {
      "interchange": "<interchange>"
    },
    "name": "staking-security_validator-slashing-protection-audit"
  }
}

Input Schema

NameRequiredDescriptionDefault
networkNonetwork, object. Optional.
pubkeysNopubkeys, array. Optional.
comparisonNocomparison, object. Optional.
interchangeYesinterchange, object. Required.

Output Schema

NameRequiredDescriptionDefault
findingsNofindings. Array.
risk_levelNorisk_level. String.
limitationsNolimitations. Array.
audit_statusNoaudit_status. String.
missing_recordsNomissing_records. Array.
duplicate_recordsNoduplicate_records. Array.
slashable_conflictsNoslashable_conflicts. Array.
validators_analyzedNovalidators_analyzed. Number.
conflicting_historiesNoconflicting_histories. Array.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Goes far beyond the annotations (readOnly, idempotent, non-destructive): it defines the conflict classes detected, enumerates audit_status and risk_level values, warns that identical records lacking signing_root are not a confirmed slash, and limits the guarantee (not a complete signing history, no protection against a later signature). It also discloses that no private key is accepted, no beacon node is queried, the price, and that an unpaid call returns x402 terms without running — all material behavior for the caller.

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?

Purpose and preconditions are front-loaded, followed by definitions, status enums, caveats, and billing. It is dense and mostly earns its length, though the status/risk value enumerations and payment detail read as a slightly padded list.

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

Completeness5/5

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

For a nested, multi-parameter audit tool with an output schema, the description covers everything an agent needs: what is validated, what the results mean, the limits of the guarantee, and the payment/auth gate. Return value details are rightly left to the output schema while the status enums are summarized for planning.

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?

With 100% schema description coverage the baseline is 3, but the description adds domain meaning that the schema lacks: it explains that slot collisions across differing blocks constitute a double proposal and that source/target epoch ordering defines surround votes, giving semantics to the signed_blocks and signed_attestations fields. It says nothing about the purpose of the optional comparison, pubkeys, or network parameters, so it stops short of a 5.

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?

States a specific verb and resource (check EIP-3076 version 5 slashing-protection interchanges) plus the timing context (before validator history is imported or reused). This makes the tool clearly distinguishable from the sibling key-deployment-conflict and withdrawal-credential audits.

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?

The description specifies when to call it: before validator history is imported or reused, and it limits scope to caller-supplied interchanges. It doesn't explicitly name when not to use it or point to an alternative tool, so it falls short of the top score.

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