Skip to main content
Glama

Score cross-network slashing correlation

restaking-risk_slashing-correlation
Read-onlyIdempotent

Cap each operator's network weights at 100 percent of its stake, then weight that exposure by stake. The correlation score is the share of stake that sits on more than one network. Weights are the caller's risk weights. No stake is fetched. Price $0.04 USDC. POST /api/v1/restaking-risk/slashing-correlation. 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": {
      "operators": "<operators>"
    },
    "name": "restaking-risk_slashing-correlation"
  }
}

Input Schema

NameRequiredDescriptionDefault
operatorsYesoperators, array. Required.

Output Schema

NameRequiredDescriptionDefault
correlation_risk_scoreNocorrelation_risk_score. Number.
maximum_slashing_exposure_percentageNomaximum_slashing_exposure_percentage. Number.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already cover read-only, idempotent, and non-destructive behavior, yet the description still adds real context: the caller supplies the risk weights, no stake is fetched, the call costs $0.04 USDC, and an unpaid call returns x402 payment terms without executing. That payment-gate behavior is exactly the kind of trait annotations cannot express.

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?

Sentences are short and front-loaded with the scoring method, then move to cost, endpoint, and failure mode. The telegraphic phrasing ('No stake is fetched') costs a little clarity but every line carries information.

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 one-parameter analytic tool with an output schema, the description covers the computation, the input semantics, the endpoint, the price, and the unpaid-call failure mode. Only the comparison to the sibling exposure tool is 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 meaning the schema lacks: 'weight' is the caller's risk weight, and weights are capped at 100 percent of stake. It does not explain how the resulting score is scaled or what the operators array ordering implies, keeping it out of 5 territory.

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 states a concrete operation — capping per-operator network weights and computing the share of stake on more than one network — which is far more specific than the title alone. It does not name a sibling or draw an explicit boundary, so it stops 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 Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no statement of when to choose this scoring tool over restaking-risk_cross-network-slashing-exposure or the other siblings. The only implicit signal is 'No stake is fetched', which hints at a contrast but never turns it into 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