Skip to main content
Glama

validator analyzer

validator-analyzer
Read-onlyIdempotent

Ethereum validator health verdict: slashing, status, balance-vs-effective -> HEALTHY/CAUTION/AVOID Price: $0.02 per call, USDC on Base via x402.

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": {
      "validator": "<validator>"
    },
    "name": "validator-analyzer"
  }
}

Input Schema

NameRequiredDescriptionDefault
validatorYesvalidator index or pubkey (required)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior4/5

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

Annotations already declare read-only, idempotent, open-world, and non-destructive behavior. The description adds important context beyond annotations by disclosing the price ($0.02 per call) and payment mechanism (USDC on Base via x402), which is critical for invocation. It does not contradict the annotations.

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 a single, front-loaded sentence that covers purpose, output categories, and cost with minimal waste. The pricing information is appended after the verdict without a clear separator, which slightly reduces readability but remains efficient.

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 simple one-parameter read-only tool with no output schema, the description provides the purpose, output categories, and pricing. It does not explain error behavior or edge cases, but those are minor given the tool's simplicity and the presence of annotations.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The input schema has 100% description coverage, fully documenting the single 'validator' parameter as index or pubkey. The description adds no additional parameter semantics, so the baseline score of 3 is appropriate.

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 specific resource (Ethereum validator) and output (HEALTHY/CAUTION/AVOID) based on slashing, status, and balance-vs-effective. It does not explicitly reference any sibling tool, so it misses the highest bar for sibling differentiation, but the resource is distinctive enough for an agent to identify the tool's function.

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?

The description offers no when-to-use guidance, no exclusions, and no mention of alternative tools. An agent must infer that this is for validator health checks from the purpose alone.

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