Skip to main content
Glama

Score exit timing before a slash

restaking-risk_exit-window
Read-onlyIdempotent

Subtract the unbonding time and the withdrawal delay from the soonest caller-supplied slash horizon. The buffer is that remainder in hours. The feasibility score is the buffer divided by the soonest horizon, and it is zero when the buffer is negative. No queue is read from a network. Price $0.04 USDC. POST /api/v1/restaking-risk/exit-window. 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": {
      "unbonding_hours": "<unbonding_hours>",
      "withdrawal_delay_hours": "<withdrawal_delay_hours>",
      "events": "<events>"
    },
    "name": "restaking-risk_exit-window"
  }
}

Input Schema

NameRequiredDescriptionDefault
eventsYesevents, array. Required.
unbonding_hoursYesunbonding hours, integer, from 0 to 8760. Required.
withdrawal_delay_hoursYesunbonding hours, integer, from 0 to 8760. Required.

Output Schema

NameRequiredDescriptionDefault
time_buffer_hoursNotime_buffer_hours. Number.
exit_feasibility_scoreNoexit_feasibility_score. Number.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

With annotations already declaring readOnly, idempotent and non-destructive, the description still adds substantive behavior: it discloses pricing ($0.04 USDC), the transport (POST /api/v1/restaking-risk/exit-window), and the x402 gating rule that an unpaid call returns payment terms without running. It also defines the boundary condition (score is zero when the buffer is negative) and that computation is caller-supplied rather than network-read. Minor gap: no statement about error handling for malformed events.

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?

Four short sentences, front-loaded with the computation, then the scoring rule, then the scope disclaimer, then payment and transport details. Every sentence carries information an agent needs and none is padding.

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 3-parameter computational endpoint with a full output schema, the description covers the operation, the scoring formula, pricing and failure mode of unpaid calls. It omits when to prefer it over the related slashing tools and how the per-event network field factors in, which are the only real 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 coverage is 100%, so the baseline is 3; the description earns more because it explains the roles the parameters play, naming unbonding_hours and withdrawal_delay_hours as subtrahends and defining the reduction over events as the 'soonest caller-supplied slash horizon'. The only unexplained element is the per-event 'network' field, whose role in the aggregation is never described.

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 concrete verb-and-resource pair ('Subtract the unbonding time and withdrawal delay from the soonest slash horizon', 'feasibility score is the buffer divided by the soonest horizon'), so an agent knows exactly what computation it performs. It also states 'No queue is read from a network,' which implicitly separates it from live risk-monitoring siblings. It does not name a sibling or state the criteria that select against one, so it falls short of a 5.

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 formula and the title ('Score exit timing before a slash', i.e. check whether an exit can complete before a slash lands), but the description never states when to call this vs. the slashing-window-feasibility or cross-network-exposure tools. No exclusions or prerequisites are given beyond the payment requirement.

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