Skip to main content
Glama

Treasury companies

treasury_companies
Read-only

Public companies holding crypto (BTC, ETH, SOL and others) on their balance sheet: market cap, NAV, mNAV and holdings per token, 50 per page. Totals cover every company, not just the page. Free data from AlphaGrowth (alphagrowth.io).

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

Input Schema

NameRequiredDescriptionDefault
pageNoPage number, 50 companies per page.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=false, so safety is covered; the description adds non-obvious behavior instead — 50 records per page and the fact that totals span all companies rather than the current page. It also discloses the data source (AlphaGrowth), though it says nothing about data freshness or update cadence.

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?

One dense sentence with the resource and metrics front-loaded, followed by the pagination/aggregation caveat and attribution. Nothing is redundant, but the field list and attribution make it slightly crowded.

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?

With no output schema, the description carries the output burden and does so by naming the metrics returned, the page size, and the totals semantics. Freshness, units/currency for market cap and NAV, and sort order are unstated, leaving minor gaps.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The single parameter is fully documented in the schema, so the baseline is 3; the description goes further by explaining that the page size is 50 and that aggregate totals are page-independent, which changes how an agent should interpret paginated results.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names a specific resource (public companies holding BTC, ETH, SOL and others on their balance sheet) and enumerates the returned metrics (market cap, NAV, mNAV, holdings per token). That resource is clearly distinct from the DAO-treasury siblings, so an agent can route without opening a schema.

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?

Usage is implied by the resource statement: use this for corporate crypto treasury data. There is no explicit when-to-use/when-not guidance relative to alternatives such as dao_treasuries, and no prerequisites or scope exclusions are stated.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources