NythosX Agent Tools

get_native_token_price

USD price of a chain's native token, no gas data. Just the native-token USD price (ETH, POL or SOL), sourced from MEXC/Gate.io/Coinbase with the same price feed get_gas_price uses. Use this when you only need the asset price, not fees — get_gas_price and compare_gas_costs already return nativeUsd alongside gas data, so call this instead only to skip the gas lookup (e.g. valuing a wallet balance, not estimating a transaction). Costs $0.001 USDC per call (x402).

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": {
      "chain": "<chain>"
    },
    "name": "get_native_token_price"
  }
}

Input Schema

Name	Required	Description	Default
`chain`	Yes	Chain to query

Schema Changelog

Changes observed during successful MCP inspections.

AddedOct 27, 2026

TDQS

A4.4/5.0

Behavior4/5

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

With no annotations, the description carries the disclosure burden well: it says there is no gas data, identifies the price sources, notes the same feed as get_gas_price, and states the per-call cost. It does not explain payment/auth mechanics beyond cost or failure behavior, so it falls short of full transparency.

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 key purpose and scoping are front-loaded, and the cost is placed at the end. There is some repetition around 'no gas data' and 'just the native-token USD price,' but the structure remains efficient overall.

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?

For a simple one-parameter read tool with no output schema, the description is complete enough: it explains the returned value as a USD price, what is excluded, where the price comes from, when to use it instead of sibling tools, and the call cost.

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 chain parameter and its enum are already fully documented. The description adds useful examples of native tokens but does not add syntax, format, or behavior details for the parameter beyond what the schema provides.

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 verb and resource: returns the USD price of a chain's native token. It explicitly distinguishes this from gas-cost tools and names the assets and price sources, so an agent can identify it without opening the schema.

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 gives explicit when-to-use guidance and names alternatives: use this only when you need the asset price and not fees, because get_gas_price and compare_gas_costs already include nativeUsd. It even provides a concrete example such as valuing a wallet balance.

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?