Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

coingecko_treasuries

Fetch normalized crypto treasury entity rows by asset, holder type, and quote currency, with row limits, from public treasuries tables.

Instructions

CoinGecko crypto treasuries. Returns normalized entity rows from CoinGecko's public crypto treasuries tables. This endpoint supports the documented vs_currency enum.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
assetNoTreasury asset filter, default all
limitNoRows to return, default 100, max 100
holder_typeNoTreasury holder type filter, default all
vs_currencyNoQuote currency

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv1.17.5
    • addedInput schema / properties / asset / enum
      Added value: +[
+  "all",
+  "bitcoin",
+  "ethereum",
+  "solana",
+  "bnb",
+  "xrp",
+  "tron"
+]
    • addedInput schema / properties / holder_type / enum
      Added value: +[
+  "all",
+  "companies",
+  "governments"
+]
    • addedInput schema / properties / vs_currency / enum
      Added value: +[
+  "btc",
+  "eth",
+  "ltc",
+  "bch",
+  "bnb",
+  "eos",
+  "xrp",
+  "xlm",
+  "link",
+  "dot",
+  "yfi",
+  "sol",
+  "usd",
+  "aed",
+  "ars",
+  "aud",
+  "bdt",
+  "bhd",
+  "bmd",
+  "brl",
+  "cad",
+  "chf",
+  "clp",
+  "cny",
+  "czk",
+  "dkk",
+  "eur",
+  "gbp",
+  "gel",
+  "hkd",
+  "huf",
+  "idr",
+  "ils",
+  "inr",
+  "jpy",
+  "krw",
+  "kwd",
+  "lkr",
+  "mmk",
+  "mxn",
+  "myr",
+  "ngn",
+  "nok",
+  "nzd",
+  "php",
+  "pkr",
+  "pln",
+  "rub",
+  "sar",
+  "sek",
+  "sgd",
+  "thb",
+  "try",
+  "twd",
+  "uah",
+  "vef",
+  "vnd",
+  "zar",
+  "xdr",
+  "xag",
+  "xau",
+  "bits",
+  "sats"
+]
  2. First observedv1.0.0

TDQS

B3/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It only states that it returns normalized rows, which is minimal. It does not disclose whether the operation is read-only (implied but not stated), any authentication needs, rate limits, or what happens with default parameters. For a data retrieval tool, this is a significant gap.

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

Conciseness3/5

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

The description is short (two sentences) but the last sentence 'This endpoint supports the documented vs_currency enum' is redundant with the schema and adds no value. The first sentence is concise and front-loaded, but the extra sentence wastes space. It is not overly verbose, but it could be tightened.

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

Completeness2/5

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

Without an output schema, the description should clarify what the returned entity rows contain. It only says 'normalized entity rows' without specifying fields or structure. It also does not explain default behavior of parameters (though the schema covers that) or the overall purpose of the data (e.g., who holds crypto). For a tool with no output schema, this is incomplete.

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?

The input schema has 100% coverage, with descriptions for all four parameters (asset, limit, holder_type, vs_currency). The description only mentions the vs_currency enum, which is already documented in the schema. It adds no additional meaning or syntax details beyond what the schema provides, so the baseline of 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 resource ('crypto treasuries') and an action ('returns normalized entity rows'). It is clearly distinct from sibling coingecko tools by its subject matter, though it doesn't name a specific alternative to differentiate against. The phrase 'normalized entity rows' is slightly ambiguous but the core purpose is clear.

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

Usage Guidelines3/5

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

The description implies when to use it – when treasury data is needed – but provides no explicit guidance on when not to use it or which sibling tools to prefer. With many coingecko siblings, this is a gap, but the resource name and description make the use case fairly obvious.

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

Deploy Server

Other Tools