Skip to main content
Glama
IAcomunIA

CoinGecko MCP Server

by IAcomunIA

get_transaction_history_public_treasury

Read-only

Query cryptocurrency transaction history for public companies and governments by Entity ID to track holdings, values, and transaction types.

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 query public companies & governments' cryptocurrency transaction history by Entity ID

Response Schema

{
  $ref: '#/$defs/public_treasury_get_transaction_history_response',
  $defs: {
    public_treasury_get_transaction_history_response: {
      type: 'object',
      properties: {
        transactions: {
          type: 'array',
          items: {
            type: 'object',
            properties: {
              average_entry_value_usd: {
                type: 'number',
                description: 'average entry value in usd after the transaction'
              },
              coin_id: {
                type: 'string',
                description: 'coin ID'
              },
              date: {
                type: 'number',
                description: 'transaction date in UNIX timestamp'
              },
              holding_balance: {
                type: 'number',
                description: 'total holding balance after the transaction'
              },
              holding_net_change: {
                type: 'number',
                description: 'net change in holdings after the transaction'
              },
              source_url: {
                type: 'string',
                description: 'source document URL'
              },
              transaction_value_usd: {
                type: 'number',
                description: 'transaction value in usd'
              },
              type: {
                type: 'string',
                description: 'transaction type: buy or sell',
                enum: [                  'buy',
                  'sell'
                ]
              }
            }
          }
        }
      }
    }
  }
}

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
entity_idYes
coin_idsNofilter transactions by coin IDs, comma-separated if querying more than 1 coin *refers to [`/coins/list`](/reference/coins-list).
orderNouse this to sort the order of transactions, default: `date_desc`
pageNopage through results, default: `1`
per_pageNototal results per page, default: `100` Valid values: 1...250
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/).
Behavior4/5

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

The description adds valuable behavioral context beyond the annotations. While annotations provide 'readOnlyHint: true', the description explains performance considerations (using 'jq_filter' to reduce response size) and hints at potential large data volumes. It doesn't contradict annotations and offers practical insights that help an agent use the tool effectively, though it could mention pagination or rate limits for a higher score.

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 front-loaded with practical advice on 'jq_filter', which is useful, but it includes an embedded JSON output schema that duplicates structured data, reducing conciseness. The first two sentences are efficient, but the schema inclusion adds unnecessary length without adding value beyond what could be in an output schema field, making it somewhat bloated.

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?

Given the tool's complexity (6 parameters, 83% schema coverage, no output schema), the description is reasonably complete. It covers purpose, usage tips, and includes an output schema in the description to compensate for the lack of a structured output schema. However, it could be more thorough by explaining error cases or linking to sibling tools, but it's adequate for the context.

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?

With schema description coverage at 83%, the input schema already documents most parameters well. The description doesn't add significant semantic details about parameters beyond what's in the schema, such as explaining 'entity_id' further or providing examples for 'coin_ids'. It mentions 'jq_filter' in usage guidelines but doesn't elaborate on its semantics beyond the schema's description, so it meets the baseline for high 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 public companies & governments' cryptocurrency transaction history by Entity ID'. It specifies the verb ('query'), resource ('transaction history'), and scope ('public companies & governments'), which is specific and actionable. However, it doesn't explicitly differentiate from sibling tools like 'get_holding_chart_public_treasury', which might provide related but different data, keeping it from a perfect score.

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

Usage Guidelines4/5

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

The description provides clear usage guidance by emphasizing the importance of using the 'jq_filter' parameter to reduce response size and improve performance, with a note to omit only if unnecessary. This gives practical advice on when to use this parameter. However, it lacks explicit guidance on when to use this tool versus alternatives (e.g., sibling tools like 'get_holding_chart_public_treasury'), which prevents a score of 5.

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