Skip to main content
Glama

size_fibre_node

Size the extra hardware a Celestia Fibre node needs on top of a validator, from the validator's share of voting power: storage rows, disk, sustained ingress, monthly inbound traffic, RAM and the uplink to order. A port of the Celestia Foundation's public Fibre calculator as Pulse implements it, calibrated to Mocha. A sizing calculator, not live network data; the output links to the Pulse page that lists the servers for this plan.

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": {
      "stake_share_pct": "<stake_share_pct>"
    },
    "name": "size_fibre_node"
  }
}

Input Schema

NameRequiredDescriptionDefault
throughputNocurrent = Mocha-level, the only presetcurrent
retention_hoursNoBlob retention window the store must cover (calculator default 4 h)
stake_share_pctYesYour share of consensus voting power in percent, e.g. 1 for 1%
bandwidth_allowance_pctNoShare of your uplink you let Fibre use; sizes the recommended port (default 20%)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / throughput / description
      Previous value: -"current = Mocha-level; november_preview = unconfirmed 15x estimate for a possible 2.2 GB/s target"New value: +"current = Mocha-level, the only preset"
    • changedInput schema / properties / throughput / enum
      Previous value: -[
      -  "current",
      -  "november_preview"
      -]New value: +[
      +  "current"
      +]
  2. Added

TDQS

A3.9/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full burden, and it does disclose meaningful behavior: it is a port of the Celestia Foundation's public calculator as Pulse implements it, calibrated to Mocha, and is not live data. It also notes the output links to a Pulse page listing servers for the plan. It does not state that the call is a pure side-effect-free computation or how results are formatted/unit-labeled, which matters for a no-annotation tool.

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 sizing scope and output list are front-loaded in the first sentence, and the provenance/caveat sentences are short and informative. Slightly dense phrasing ('the uplink to order') costs a bit of clarity, but nothing is wasted.

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?

With no output schema, the description does the work of naming what comes back (the resource rows plus a link to the Pulse server list) and flags that values are calculator estimates rather than live measurements. For a 4-parameter, no-annotation tool this is nearly complete; units and the exact response shape remain unstated.

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%, so the baseline is 3. The description adds a little causal framing by saying sizing derives from the validator's share of voting power and that the uplink to order depends on the allowed bandwidth share, but it never mentions retention_hours or the throughput preset, so it adds only marginal meaning 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?

States a specific verb (size) and resource (extra hardware for a Celestia Fibre node on top of a validator) and enumerates the outputs produced: storage rows, disk, sustained ingress, monthly inbound traffic, RAM, and uplink/port. The clause 'A sizing calculator, not live network data' separates it from live-state siblings such as get_fibre_network_status or get_celestia_hardware_usage.

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?

Clearly frames the use case (planning hardware for a Fibre node given a validator's voting-power share) and explicitly excludes the wrong use case ('not live network data'), which routes agents away from status/usage tools. It stops short of naming a specific alternative sibling or stating prerequisites such as when a plan already exists.

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