Skip to main content
Glama

Check slashing window feasibility

restaking-risk_slashing-window-feasibility
Read-onlyIdempotent

Compare caller-supplied slashing stages with an available window. Each duration is an integer in seconds, or in epochs when its unit is epochs. Epoch length is seconds. Stages run in detection, evidence, submission, veto, execution, and finality order. Consecutive stages listed in parallel start together and the timeline uses the longest. A missing stage is incomplete and is not treated as zero. feasibility_status is feasible, margin_exceeded, infeasible, incomplete, or invalid. A fit is arithmetic only. No protocol parameters are fetched. Price $0.05 USDC. POST /api/v1/restaking-risk/slashing-window-feasibility. 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": {
      "epoch": "<epoch>",
      "window": "<window>"
    },
    "name": "restaking-risk_slashing-window-feasibility"
  }
}

Input Schema

NameRequiredDescriptionDefault
vetoNoveto, object. Optional.
epochYesepoch, object. Required.
marginNomargin, object. Optional.
windowYesepoch, object. Required.
evidenceNoevidence, object. Optional.
finalityNofinality, object. Optional.
parallelNoparallel, array. Optional.
detectionNodetection, object. Optional.
executionNoexecution, object. Optional.
submissionNosubmission, object. Optional.
alternativesNoalternatives, array. Optional.

Output Schema

NameRequiredDescriptionDefault
slackNoslack. Object.
stagesNostages. Array.
assumptionsNoassumptions. Array.
bottlenecksNobottlenecks. Array.
alternativesNoalternatives. Array.
infeasibilityNoinfeasibility. Array.
safety_marginNosafety_margin. Object.
missing_stagesNomissing_stages. Array.
total_requiredNototal_required. Object.
available_windowNoavailable_window. Object.
feasibility_statusNofeasibility_status. String.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Beyond the read-only, idempotent, open-world annotations, the description discloses important behavior: arithmetic-only evaluation, no protocol parameters fetched, payment of $0.05 USDC, and that an unpaid call returns x402 payment terms without running. It also explains stage ordering, parallel stage semantics, and incomplete-stage handling. The main missing behavioral context is how the alternatives input is processed.

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 purpose and then systematically covers units, stage order, parallel behavior, missing stages, feasibility statuses, and payment mechanics. It is longer than many definitions but most sentences carry operational value for this paid, multi-parameter endpoint. A little tightening could improve it, but it is not bloated.

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

Completeness3/5

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

The description covers the core arithmetic model, stage semantics, feasibility statuses, and payment behavior, which is substantial for an 11-parameter tool. However, it does not explain what margin means or how the alternatives array is used, leaving meaningful schema fields without semantic guidance. With an output schema present, return-value coverage is adequate, but input completeness has clear gaps.

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 description coverage is 100%, so the baseline is 3, but the description adds real meaning: durations are integer seconds or epochs when unit is epochs, epoch length is seconds, stages run in a specific order, and parallel stages start together using the longest duration. It omits explanation of the margin and alternatives parameters, which are documented only generically in the schema.

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 description gives a specific verb and resource: 'Compare caller-supplied slashing stages with an available window.' That is clear enough for an agent to know what the tool does. It does not explicitly name or differentiate against sibling tools such as exit-window or slashing-correlation, so it falls short of the top score.

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 purpose and by the caveat 'A fit is arithmetic only. No protocol parameters are fetched.' However, the description never states when to choose this tool over the slashing-correlation or exit-window siblings, nor does it give explicit exclusions. This is minimum viable guidance.

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