Skip to main content
Glama
IAcomunIA

CoinGecko MCP Server

by IAcomunIA

get_holding_chart_public_treasury

Read-only

Query historical cryptocurrency holdings charts for public companies and governments to analyze investment trends and portfolio changes over time.

Instructions

When using this tool, always use the jq_filter parameter to reduce the response size and improve performance.

Only omit if you're sure you don't need the data.

This endpoint allows you to query historical cryptocurrency holdings chart of public companies & governments by Entity ID and Coin ID

Response Schema

{
  $ref: '#/$defs/public_treasury_get_holding_chart_response',
  $defs: {
    public_treasury_get_holding_chart_response: {
      type: 'object',
      properties: {
        holding_value_in_usd: {
          type: 'array',
          items: {
            type: 'array',
            items: {
              type: 'number'
            }
          }
        },
        holdings: {
          type: 'array',
          items: {
            type: 'array',
            items: {
              type: 'number'
            }
          }
        }
      }
    }
  }
}

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
entity_idYes
coin_idYes
daysYesdata up to number of days ago Valid values: `7, 14, 30, 90, 180, 365, 730, max`
include_empty_intervalsNoinclude empty intervals with no transaction data, default: false
jq_filterNoA jq filter to apply to the response to include certain fields. Consult the output schema in the tool description to see the fields that are available. For example: to include only the `name` field in every object of a results array, you can provide ".results[].name". For more information, see the [jq documentation](https://jqlang.org/manual/).
Behavior3/5

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

Annotations provide readOnlyHint=true, indicating this is a safe read operation. The description adds useful behavioral context about performance optimization with jq_filter and mentions the endpoint's purpose, but doesn't disclose other important traits like rate limits, authentication needs, or what happens with invalid parameters. No contradiction with annotations exists.

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 moderately concise but includes a performance tip that's somewhat front-loaded. The inclusion of a JSON output schema in the description text is redundant and adds unnecessary length, as this information should be in structured fields. The core purpose statement is clear but could be more streamlined.

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?

Given the tool's complexity (5 parameters, historical data query) and annotations covering safety, the description provides basic purpose and a performance tip. However, it lacks output explanation (no output schema provided), doesn't clarify error conditions, and offers minimal usage context. It's adequate but has clear gaps for a data retrieval tool.

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 60%, with three parameters well-described (days, include_empty_intervals, jq_filter) and two undocumented (entity_id, coin_id). The description mentions Entity ID and Coin ID but doesn't add format or semantics beyond the schema. It emphasizes jq_filter usage, which aligns with schema documentation. Baseline 3 is appropriate given partial schema coverage.

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 clearly states the tool's purpose: 'query historical cryptocurrency holdings chart of public companies & governments by Entity ID and Coin ID'. This specifies the verb ('query'), resource ('historical cryptocurrency holdings chart'), and scope ('public companies & governments'). However, it doesn't explicitly distinguish this tool from sibling tools like 'get_transaction_history_public_treasury', which appears related but isn't directly contrasted.

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?

The description provides some guidance about using the 'jq_filter' parameter for performance, but offers no explicit when-to-use or when-not-to-use instructions. It doesn't mention alternatives or prerequisites, and doesn't clarify how this tool differs from other public treasury or chart-related tools in the sibling list.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/IAcomunIA/MCP_firts'

If you have feedback or need assistance with the MCP directory API, please join our Discord server