Skip to main content
Glama

DERO MCP Server

by io.github.DHEBP
OverviewDiscussionsAdmin

verify_supply

Read-only

Composite: recompute DERO total supply offline via CalcSupply (premine + one-time launch credit + Σ CalcBlockReward epochs — DEROFDN community-dev / dero-docs schedule), optionally cross-check against DERO.GetInfo.total_supply.

When to call: when the user asks "what is the total supply", "does GetInfo match the schedule", "verify the supply", or wants an independent recompute that does not trust a node. PREFER this over reading GetInfo alone — GetInfo on older builds can undercount after halvings (display quirk, not inflation). PREFER citing the returned related_docs (integrity/verify-the-supply).

Input Requirements:

  • height is OPTIONAL. Non-negative integer topoheight/height. Default: tip topoheight from DERO.GetInfo.

  • If the daemon is unreachable you MUST pass height — otherwise the tool returns RPC_UNREACHABLE / INVALID_INPUT.

Output: { height, height_source, calc_supply_atoms, calc_supply_dero, block_reward_atoms, block_reward_dero, getinfo_total_supply, match, formula_note, narrative, related_docs, _diagnostics }. match is true/false when GetInfo.total_supply is present, else null. Scope is schedule CalcSupply only — NOT a UTXO census.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
heightNoTopoheight / height to evaluate. Default: tip topoheight from DERO.GetInfo. Required when the daemon is unreachable.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • changedInput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
    • removedInput schema / additionalProperties
      Removed value: -false
    • addedInput schema / properties / height / maximum
      Added value: +9007199254740991
  2. Added

TDQS

A4.7/5.0
Behavior5/5

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

Annotations already mark readOnlyHint=true, but the description adds substantial context: the computation is offline, the optional cross-check behavior, the halving undercount display quirk, the exact error conditions if daemon is unreachable without a height, and the limited scope to schedule CalcSupply. This goes well beyond the annotation safety profile.

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 structured with clear sections: purpose, when to call, input requirements, and output. It front-loads the most decision-relevant information and every sentence adds value—such as the preference over GetInfo and the error condition. Length is justified by the tool's composite nature.

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 output schema, the description fully explains the return shape, including the meaning of 'match', and provides related_docs. It covers error behavior, defaults, scope limitations, and the offline recompute approach. An agent has all the context needed to invoke and interpret this tool correctly.

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 description coverage is 100% and already explains height's default and the requirement when the daemon is unreachable. The description mostly repeats that information, adding only the concrete error outcome. Since the schema carries the parameter semantics, no additional meaning is needed, so the baseline of 3 holds.

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 opens with a specific verb and resource: 'recompute DERO total supply offline via CalcSupply' and 'cross-check against DERO.GetInfo.total_supply.' It clearly distinguishes itself from GetInfo by stating 'PREFER this over reading GetInfo alone,' so an agent can identify this tool's unique role among siblings.

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

Usage Guidelines5/5

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

The 'When to call' section explicitly lists trigger queries, then gives a concrete comparison to the alternative: GetInfo can undercount after halvings on older builds. It also excludes a non-goal ('NOT a UTXO census') and specifies the required height condition for unreachable daemons. This leaves no ambiguity about when to choose this tool.

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

All DERO MCP Server 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