Skip to main content
Glama

get_dao_treasury_benchmark

Read-only

DAO treasury benchmarks — top DAOs by treasury size, stablecoin percentage, runway, and governance token concentration. Median benchmarks: $550M treasury, 61% stablecoin, 48-month runway. Source: DeepDAO public data. $0.02 USDC per call.

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

Input Schema

NameRequiredDescriptionDefault
sort_byNo
min_treasury_usdNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.2/5.0
Behavior4/5

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

Annotations already establish readOnlyHint=true, openWorldHint=true and destructiveHint=false, so safety is covered. The description goes beyond them usefully by disclosing the data source (DeepDAO public data) and, critically, a per-call price of $0.02 USDC — a cost trait an agent needs before invoking. It omits freshness/staleness of the snapshot and the shape of the response, which keeps it from a 5.

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 definition is front-loaded with the substantive content (what the benchmark covers) and then terse metadata on medians, source and price. Every sentence is short and earns roughly its place, though the specific median figures are illustrative rather than operational and could be trimmed.

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?

With no output schema, the description does well to enumerate the four returned dimensions and to disclose source and cost. However, for a tool with two entirely undescribed parameters and no stated return structure (list of DAOs? aggregates?), an agent still lacks what it needs to call the tool precisely, leaving it only minimally adequate.

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

Parameters2/5

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

Schema description coverage is 0% for two parameters, so the description must carry the burden and it does not: neither sort_by nor min_treasury_usd is mentioned. The phrases 'treasury size' and 'stablecoin percentage' loosely echo the two enum values but never explain that they are sort options, nor what min_treasury_usd filters or in what unit.

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 names a specific resource — DAO treasury benchmarks — and enumerates the dimensions returned (treasury size, stablecoin percentage, runway, governance token concentration). That is enough to distinguish it from sibling benchmarks such as get_chain_tvl_benchmark or get_defi_yield_benchmark without opening the schema, though it never states a verb or an explicit contrast with those siblings.

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 guidance on when to use this versus the many other benchmark tools, no stated prerequisites, and no exclusions. The only context is a set of median figures, which is background data rather than usage instruction; the agent must infer that this is the DAO-treasury comparison endpoint from the title alone.

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