Skip to main content
Glama

BRAINIAC Staking Security

Audit validator withdrawal credentials

staking-security_validator-withdrawal-credential-audit
Read-onlyIdempotent

Compare caller-supplied Ethereum validator withdrawal credentials with expected types, withdrawal addresses, and ownership mappings. 0x00 is a BLS credential and the other 31 bytes are a hash fragment, not an address. 0x01 and 0x02 decode an execution address only when the next 11 bytes are zero. audit_status is valid, mismatched, warnings, invalid, or incomplete. risk_level is low, medium, high, or critical. A match is not proof of control and was not read from a beacon node. Price $0.05 USDC. POST /api/v1/staking-security/validator-withdrawal-credential-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": {
      "validators": "<validators>",
      "expected": "<expected>"
    },
    "name": "staking-security_validator-withdrawal-credential-audit"
  }
}

Input Schema

NameRequiredDescriptionDefault
policyNopolicy, object. Optional.
networkNonetwork, string, length 1 to 80. Optional.
expectedYesexpected, array. Required.
ownershipNoownership, array. Optional.
validatorsYesvalidators, array. Required.

Output Schema

NameRequiredDescriptionDefault
findingsNofindings. Array.
risk_levelNorisk_level. String.
limitationsNolimitations. Array.
audit_statusNoaudit_status. String.
missing_validatorsNomissing_validators. Array.
duplicate_destinationsNoduplicate_destinations. Array.
credential_type_summaryNocredential_type_summary. Array.
unexpected_destinationsNounexpected_destinations. Array.
withdrawal_destinationsNowithdrawal_destinations. Array.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior5/5

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

Beyond the read-only and idempotent annotations, the description adds critical behavior: data was not read from a beacon node, a match does not prove control, the audit_status and risk_level value spaces, the $0.05 USDC charge, and that unpaid calls return x402 payment terms without running.

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?

The description is dense but front-loaded: purpose first, then credential decoding rules, result enums, evidentiary caveat, payment terms, and endpoint. Every sentence carries operational value, with no filler.

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 nested five-parameter audit with an output schema, the description covers the most important behavioral context: provenance, interpretation limits, result values, payment gating, and endpoint. It leaves policy and network parameter semantics to the schema, which is reasonable at 100% coverage, but a little more detail on ownership policy handling would make it fully complete.

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 domain meaning beyond the schema: 0x00 is a BLS credential with a 31-byte hash fragment, and 0x01/0x02 decode an execution address only when the next 11 bytes are zero. It does not explain policy, network, or ownership-field semantics, but it materially enriches the withdrawal-credential parameter.

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 names a specific verb and resource: comparing caller-supplied Ethereum validator withdrawal credentials against expected types, withdrawal addresses, and ownership mappings. That is precise enough to distinguish this audit from the sibling key-deployment conflict and slashing-protection audits.

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?

Usage is implied by the comparison framing, and the caveat that a match is not proof of control helps interpretation. However, the description does not explicitly say when to choose this tool versus the slashing-protection audit or when it is not appropriate.

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