Skip to main content
Glama

Get FlareWatch Validator

get_flarewatch_validator
Read-only

Return FlareWatch's own Flare P-Chain validators — same scoring algorithm as every other validator, no promotional weighting. One row per node (label, self-bond, delegations, stake count, fee, uptime, expiry, Score) plus entity totals. is_live=false marks a cold-load fallback row whose live figures are not measurements.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_flarewatch_validator"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior5/5

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

Beyond the readOnlyHint already declaring this a safe read, the description adds valuable behavioral context: one row per node, the exact fields returned, entity totals, and the critical caveat that is_live=false indicates a cold-load fallback whose figures are not live measurements. This data-quality disclosure is exactly what an agent needs before interpreting results.

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?

The definition is three tight sentences, front-loads what the tool returns and its neutrality, then lists row fields, and finishes with the is_live fallback caveat. Every sentence carries relevant information with no filler.

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?

With no parameters and no output schema, the description carries the job of explaining the return shape and data-quality semantics. It does so by listing the node fields, mentioning entity totals, and warning about cold-load fallback rows, leaving no material ambiguity for a zero-argument read tool.

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?

The tool takes zero parameters, so there is no parameter semantics for the description to clarify. The baseline for a zero-parameter tool applies; the description does not need to compensate for any schema gaps.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description uses a specific verb and resource: it returns FlareWatch's own Flare P-Chain validators. The phrase 'same scoring algorithm as every other validator, no promotional weighting' clearly distinguishes this subset from the broader validator listings exposed by siblings like get_flare_validators or compare_validators.

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?

The description implies when to use it: to inspect FlareWatch's own validator nodes and their neutral scoring. However, it never explicitly names an alternative tool or states when not to use this one, so an agent must infer the routing from the sibling names and the phrase 'every other validator.'

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