Skip to main content
Glama
Sign In
r0x-os

r0x-os

by nhevers
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Check funding status

fund

Check a Robinhood Chain address balance and receive step-by-step funding instructions for a $0.01 USDG fee.

Instructions

Balance plus step-by-step funding instructions for a Robinhood Chain address. Costs $0.01 USDG.

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": {
      "address": "<address>"
    },
    "name": "fund"
  }
}

Input Schema

NameRequiredDescriptionDefault
addressYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.0

TDQS

A3.5/5.0
Behavior3/5

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

With no annotations provided, the description carries the burden of behavioral disclosure. It discloses the $0.01 USDG cost and indicates it returns balance plus instructions, but it does not specify output structure, potential side effects, or whether it actually executes a funding transaction.

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 two short sentences, front-loading the core purpose ('Balance plus step-by-step funding instructions') and adding the critical cost caveat. No wasted words.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a one-parameter read/advice tool with no output schema, the description covers the main context: target address, what to expect (balance + instructions), and cost. It lacks explicit output formatting and edge-case detail, but is minimally viable for agent invocation.

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 single 'address' parameter is defined in the schema by regex, and the description adds that this is a Robinhood Chain address, clarifying the network. However, with 0% schema coverage in the description, it does not fully compensate by explaining what the address should represent beyond the property name.

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 title 'Check funding status' and description 'Balance plus step-by-step funding instructions for a Robinhood Chain address' clearly state the tool's verb and target resource. It distinguishes itself from the 'balance' sibling by adding funding instructions, though it does not explicitly name alternatives.

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 use when a user needs balance and funding instructions for a Robinhood Chain address, and the cost warning adds context. However, it provides no explicit when-to-use/when-not-to-use guidance or references to sibling tools like 'balance' or 'r0x_setup'.

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

Deploy Server

Other Tools