Skip to main content
Glama
Sign In

BitBasic

by com.bitbasic
OverviewDiscussionsAdmin

Validator details

validator-details
Read-onlyIdempotent

One validator in full: status, stake, delegators, commission and its delegators' reward rate, how much it signed and produced, its last 100 blocks (where the network says who signed each), and how it voted on the latest governance proposals. Find its address with find-validators.

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": {
      "network": "<network>",
      "address": "<address>"
    },
    "name": "validator-details"
  }
}

Input Schema

NameRequiredDescriptionDefault
addressYesThe validator's address as BitBasic lists it (its validator id on Concordium).
networkYesA network slug from list-networks.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already establish read-only, idempotent, non-destructive behavior, so the description adds value by disclosing the returned data scope. It includes a useful caveat that last-100-block signer data depends on 'where the network says who signed each' and notes governance coverage is limited to the latest proposals. It does not mention pagination, rate limits, or freshness.

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 description is a single front-loaded sentence with no wasted wording. Every clause adds concrete return-scope information rather than restating the title or schema.

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 read-only detail tool with no output schema, the description thoroughly enumerates what is returned and qualifies the block-signer and governance coverage. It stops short of describing empty-result or error behavior, but the core call context is complete.

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?

Schema coverage is 100%, so the address and network parameters are already documented. The description adds only a sourcing hint for the address via find-validators, which is useful but marginal beyond the schema.

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 states a specific resource and scope: 'One validator in full' with enumerated data categories (status, stake, delegators, commission, signed/produced blocks, governance votes). It clearly distinguishes this detail view from find-validators by directing address discovery there.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

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

It gives explicit prerequisite guidance: 'Find its address with find-validators.' However, it does not explicitly compare against list-validators or compare-validators or state when not to use this detailed view.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All BitBasic toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources