AIsa Finance

Exchanges List with Data

get_coingecko_exchanges

Read-onlyIdempotent

This endpoint allows you to query all the supported exchanges with exchanges' data (ID, name, country, ...) that have active trading volumes on CoinGecko

Published reference price: $0.008 USD per successful request. Declared unit rate: $0 USD per provider_credit. Account-specific pricing and final settlement may differ.

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

Input Schema

Name	Required	Description	Default
`page`	No	Page through results. Default: 1
`per_page`	No	Total results per page. Default: 100. Valid values: 1...250

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed7 schema fields changedOct 15, 2026
- removedInput schema / properties / page / default
```
Removed value: -1
```
- addedInput schema / properties / page / description
```
Added value: +"Page through results. \nDefault: 1"
```
- changedInput schema / properties / page / type
```
Previous value: -"integer"New value: +"number"
```
- removedInput schema / properties / per_page / default
```
Removed value: -100
```
- addedInput schema / properties / per_page / description
```
Added value: +"Total results per page. \nDefault: 100. \nValid values: 1...250"
```
- removedInput schema / properties / per_page / maximum
```
Removed value: -250
```
- changedInput schema / properties / per_page / type
```
Previous value: -"integer"New value: +"number"
```
First observedSep 15, 2026

TDQS

B3.2/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, openWorldHint=true, and destructiveHint=false, so the safety profile is fully covered. The description adds the meaningful behavioral constraint that only exchanges with active trading volumes are returned. The appended pricing block is harness metadata about billing, not tool behavior, so it earns no credit.

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 tool description itself is a single front-loaded sentence with no filler, and the key scope qualifier is stated up front. The only bloat is the injected pricing comment block, which is not part of the authored description.

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?

An output schema exists, so return values need not be explained, and annotations cover safety and idempotency. What remains thin is the routing relative to the near-identically named get_coingecko_exchanges_list sibling, which is the one thing an agent is most likely to get wrong.

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%, with both page and per_page documented including defaults and the 1...250 valid range, so the schema carries the parameter burden. The description adds no pagination or format detail beyond that, making the baseline 3 appropriate.

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?

States a specific verb and resource (query supported exchanges) and enumerates the returned fields (ID, name, country), which implicitly separates it from the bare get_coingecko_exchanges_list sibling. However, it never names that sibling, so an agent must infer the distinction from the 'with exchanges' data' phrasing rather than being told.

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

Usage Guidelines2/5

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

There is no explicit when-to-use or when-not-to-use guidance and no alternative is named. The phrase 'that have active trading volumes' hints at the result scope, but nothing tells the agent why it should pick this over get_coingecko_exchanges_list or get_coingecko_exchanges_id.

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

All AIsa Finance 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?