Skip to main content
Glama
Sign In

GadgetHumans API Hub

by com.gadgethumans
OverviewDiscussionsAdmin

token_price

[object Object]

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": {
      "Token Price - live DEX price for any token contract": "<Token Price - live DEX price for any token contract>"
    },
    "name": "token_price"
  }
}

Input Schema

NameRequiredDescriptionDefault
Token Price - live DEX price for any token contractYesParameter: Token Price - live DEX price for any token contract
token price,get token price,price of a token,dex price,contract price,base token price,liquidity,24h changeNoParameter: token price,get token price,price of a token,dex price,contract price,base token price,liquidity,24h change
Live USD price for any ERC-20 token contract address (Base, Ethereum, BSC, Arbitrum, Polygon): price, 24h change, liquidity, 24h volume, FDV and the deepest trading pair, from Dexscreener. Also accepts a ticker symbol and resolves it via CoinGecko. Use before quoting, routing or sizing a swap.NoParameter: Live USD price for any ERC-20 token contract address (Base, Ethereum, BSC, Arbitrum, Polygon): price, 24h change, liquidity, 24h volume, FDV and the deepest trading pair, from Dexscreener. Also accepts a ticker symbol and resolves it via CoinGecko. Use before quoting, routing or sizing a swap.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

D1.3/5.0
Behavior1/5

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

No annotations are provided, so the description carries the full behavioral burden, and it delivers none of it. It discloses no data source, no chain coverage, no rate limits, no failure mode for unknown contracts, and no indication of whether the call is a read-only lookup.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness1/5

Is the description appropriately sized, front-loaded, and free of redundancy?

There is no structure to evaluate: a single broken token is neither front-loaded nor informative. This is under-specification at its extreme rather than a conciseness tradeoff.

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

Completeness1/5

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

A three-parameter financial-data tool with no annotations and no output schema depends entirely on the description to be usable, and the description is empty of content. Nothing an agent needs in order to call it correctly is present.

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 reported at 100%, so the baseline is 3 even though the description contributes nothing. It should be noted the schema's own descriptions are degenerate — three near-identical free-text properties whose 'descriptions' merely restate their names — so the parameter contract is effectively opaque despite the formal coverage figure.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose1/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description is the literal string "[object Object]" — a serialization failure that communicates nothing about what the tool does. An agent cannot tell that this returns a live DEX token price, nor distinguish it from siblings like crypto, get_crypto_prices, or token_verdict.

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

Usage Guidelines1/5

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

No when-to-use, when-not-to-use, or alternative-tool guidance appears anywhere in the description. The intended guidance ('Use before quoting, routing or sizing a swap') exists only inside a mangled schema property name, not in the description an agent reads to select the tool.

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

All GadgetHumans API Hub 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