Skip to main content
Glama

Calculate cross-network slashing exposure

restaking-risk_cross-network-slashing-exposure
Read-onlyIdempotent

Calculate unique collateral, gross exposure, and overlap when caller-supplied vault collateral is reused across networks. Simultaneous scenarios slash the starting balance and cap the combined percent at 100%. Sequential scenarios reduce the remaining balance after each event. audit_status is calculated, warnings, incomplete, or invalid. Amounts are integers in the caller-supplied unit. Prices and conversion rates are used only when supplied. No balance or price is fetched. Price $0.05 USDC. POST /api/v1/restaking-risk/cross-network-slashing-exposure. 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": {
      "vaults": "<vaults>",
      "allocations": "<allocations>",
      "slashing": "<slashing>",
      "scenarios": "<scenarios>"
    },
    "name": "restaking-risk_cross-network-slashing-exposure"
  }
}

Input Schema

NameRequiredDescriptionDefault
ratesNorates, array. Optional.
reuseNoreuse, array. Optional.
pricesNoprices, array. Optional.
vaultsYesvaults, array. Required.
slashingYesslashing, array. Required.
scenariosYesscenarios, array. Required.
allocationsYesallocations, array. Required.

Output Schema

NameRequiredDescriptionDefault
warningsNowarnings. Array.
scenariosNoscenarios. Array.
assumptionsNoassumptions. Array.
audit_statusNoaudit_status. String.
concentrationNoconcentration. Array.
vault_exposureNovault_exposure. Array.
cascading_pathsNocascading_paths. Array.
network_exposureNonetwork_exposure. Array.
total_collateralNototal_collateral. Array.
unique_collateralNounique_collateral. Array.
maximum_modeled_lossNomaximum_modeled_loss. Array.
overlapping_exposureNooverlapping_exposure. Array.
total_gross_exposureNototal_gross_exposure. Array.
unique_collateral_valueNounique_collateral_value. Object.
maximum_modeled_loss_valueNomaximum_modeled_loss_value. Object.
total_gross_exposure_valueNototal_gross_exposure_value. Object.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior5/5

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

Beyond the annotations (read-only, idempotent, open-world), the description discloses the slashing math itself: simultaneous events hit the starting balance with a 100% combined cap, sequential events hit the remaining balance. It also states that no balance or price is fetched, that amounts are integers in a caller-supplied unit, and that an unpaid call returns x402 payment terms without running, priced at $0.05 USDC.

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 is front-loaded, followed by scenario semantics, then invocation and payment constraints, with no filler. The clause 'audit_status is calculated, warnings, incomplete, or invalid' is awkwardly phrased and slightly obscures the enumeration, but the overall density is good.

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 seven-parameter nested-input tool with an output schema, the description covers what the computation returns at a high level, the scenario-ordering rules, the input unit conventions, and the payment gate. Nothing an agent needs in order to invoke it correctly appears to be missing.

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 meaning: the caller-supplied unit for amounts, that prices and rates are applied only when supplied, and the behavioral difference between 'simultaneous' and 'sequential' ordering values. It also documents the audit_status outcome space that the schema does not convey.

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 opening sentence names a specific verb and resource (calculate cross-network slashing exposure) and enumerates the three quantities produced: unique collateral, gross exposure, and overlap. It does not explicitly contrast with siblings such as slashing-correlation or exit-window, so an agent must infer the boundary from the output description alone.

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?

Applicability is implied by the phrase 'when caller-supplied vault collateral is reused across networks', which frames the domain but is a mechanism description rather than routing advice. There is no explicit when-to-use, when-not-to-use, or named alternative among the sibling tools.

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