NythosX Agent Tools

list_chains

List supported chains (Base, Ethereum, Arbitrum, Optimism, Polygon, Solana) and the gas-unit constants used by the paid tools (free). Always returns the full, unfiltered list of all 6 chains (no input/filter params). gasUnits.{transfer|usdc_transfer|swap} are plain integers: the gas units a typical transaction of that type costs on an EVM chain (evm) or in Solana compute units (svm) — multiply by the chain's current fee from get_gas_price to estimate USD cost yourself, or just call get_gas_price/compare_gas_costs which already does this.

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": "list_chains"
  }
}

Input Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 21, 2026

TDQS

A4.6/5.0

Behavior4/5

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

With no annotations, the description carries the full behavioral burden and does well: it discloses that the call is free, takes no parameters, returns all six chains unfiltered, and explains the gasUnits return fields and their EVM/Solana units. It does not mention auth or rate limits, but for a free listing tool those omissions are minor.

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 purpose is front-loaded in the first sentence, and the remaining detail about gasUnits and alternatives is useful. The final sentence is dense, but it earns its space by clarifying how to use the returned constants.

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?

Because there is no output schema and no annotations, the description must explain what comes back. It does so by listing the chains, the gasUnits fields, and the units used for EVM vs Solana, and it explains how to use those values with get_gas_price or compare_gas_costs.

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 has zero parameters, so the schema baseline is 4. The description reinforces this by stating 'no input/filter params,' which is helpful but does not add much beyond the empty input 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 uses a specific verb and resource: 'List supported chains' and 'gas-unit constants used by the paid tools.' It names all six chains and clearly distinguishes the tool from get_gas_price and compare_gas_costs by explaining that those siblings perform the fee math itself.

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?

It explicitly says the tool is free, has no input/filter parameters, and always returns the full unfiltered list. It also directs the agent to get_gas_price or compare_gas_costs when the goal is estimating USD cost, which gives a clear alternative and condition for using those siblings instead.

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

All NythosX Agent Tools tools Inspect

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

Need Help?