Skip to main content
Glama

AIsa Finance

by one.aisa
OverviewDiscussionsAdmin

Coins List (ID Map)

get_coingecko_coins_list
Read-onlyIdempotent

This endpoint allows you to query all the supported coins on CoinGecko with coins ID, name and symbol

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.

Input Schema

NameRequiredDescriptionDefault
statusNoFilter by status of coins. Default: active
include_platformNoInclude platform and token's contract addresses. Default: false

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • removedInput schema / properties / include_platform / default
      Removed value: -false
    • changedInput schema / properties / include_platform / description
      Previous value: -"Include platform + contract addresses."New value: +"Include platform and token's contract addresses. \nDefault: false"
    • addedInput schema / properties / status
      Added value: +{
+  "description": "Filter by status of coins. \nDefault: active",
+  "enum": [
+    "active",
+    "inactive"
+  ],
+  "type": "string"
+}
  2. First observed

TDQS

C2.9/5.0
Behavior2/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so the safety profile is covered. The description adds no behavioral context beyond that: no rate limits, caching, pagination, or size characteristics of the full coin list, and no auth requirements.

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 core sentence is short, front-loaded, and free of padding. The appended pricing blockquote is boilerplate rather than description content, but it does not obscure the purpose.

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?

An output schema exists, so return values need not be explained, and the 100% schema coverage handles parameters. The remaining gap is routing guidance against the large sibling set, which is not addressed.

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%, so both optional parameters (status filter, include_platform) are fully documented in the schema with defaults. The description adds nothing about them, so the baseline 3 is 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?

The description states a specific verb (query) plus resource (all supported coins) and names the returned fields (ID, name, symbol), which is concrete. However, it does not differentiate itself from close siblings like get_coingecko_coins_markets or get_coingecko_coins_id, so an agent must infer that this is the flat ID/name/symbol lookup rather than price or detail data.

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 when-to-use guidance, no exclusions, and no mention of alternatives. With roughly 20 coingecko siblings, an agent gets no explicit routing signal for choosing this list endpoint over markets, id, or search.

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

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