Skip to main content
Glama

BRAINIAC Staking Security

Audit validator deployment conflicts

staking-security_validator-key-deployment-conflict-audit
Read-onlyIdempotent

Compare a caller-supplied validator deployment inventory for duplicate active public keys, simultaneous primary and backup activation, overlapping activation windows, and failover rules that disagree. Windows are absolute instants, including offsets. An inactive standby covered by an exclusive failover rule is not treated as concurrent. audit_status is clean, conflicts_detected, warnings, or incomplete. risk_level is low, medium, high, or critical. Activation status is an assertion. No host is contacted and no private key is read. Price $0.05 USDC. POST /api/v1/staking-security/validator-key-deployment-conflict-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": {
      "deployments": "<deployments>"
    },
    "name": "staking-security_validator-key-deployment-conflict-audit"
  }
}

Input Schema

NameRequiredDescriptionDefault
deploymentsYesdeployments, array. Required.
failoverRulesNofailoverRules, array. Optional.
expectedTopologyNoexpectedTopology, array. Optional.
maintenanceWindowsNomaintenanceWindows, array. Optional.

Output Schema

NameRequiredDescriptionDefault
findingsNofindings. Array.
risk_levelNorisk_level. String.
limitationsNolimitations. Array.
audit_statusNoaudit_status. String.
failover_conflictsNofailover_conflicts. Array.
affected_environmentsNoaffected_environments. Array.
concurrent_deploymentsNoconcurrent_deployments. Array.
duplicate_validator_keysNoduplicate_validator_keys. Array.
overlapping_activation_windowsNooverlapping_activation_windows. Array.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior5/5

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

The description adds substantial context beyond the read-only and idempotent annotations: it states that no host is contacted, no private key is read, payment is $0.05 USDC, and an unpaid call returns x402 terms without running. It also defines output status categories and explains how activation windows and exclusive failover rules are interpreted.

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 is front-loaded with the comparison purpose and packed efficiently into a dense paragraph with no wasted preamble. Some details, such as enumerating audit_status and risk_level, may be redundant with the output schema, but they are compact and useful enough not to undermine conciseness.

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?

Given a read-only audit with annotations, a full input schema, and an output schema, the description covers the core checks, payment behavior, non-contact guarantees, and result semantics. It is still missing guidance on when to choose this audit over sibling audits and how the optional topology and maintenance inputs influence results.

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 semantic meaning beyond the schema by specifying that windows are absolute instants including offsets, that activation status is an assertion, and that an inactive standby under an exclusive failover rule is not concurrent. It does not explain how the optional expectedTopology and maintenanceWindows inputs affect the audit, so it stops short of full parameter guidance.

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: comparing a validator deployment inventory for duplicate active public keys, simultaneous primary/backup activation, overlapping windows, and disagreeing failover rules. This clearly distinguishes it from the sibling slashing-protection and withdrawal-credential audits by focusing on deployment conflicts.

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 the tool is used to audit deployment inventories for conflicts, but it gives no explicit when-to-use guidance, prerequisites, or comparison to sibling audits. Usage is inferable from the purpose, but the agent is left to decide on its own when this audit is the right choice.

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