Skip to main content
Glama

Stratalize Intelligence

Get Dao Treasury Benchmark

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
Behavior3/5

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

Annotations already cover the safety profile (readOnlyHint=true, destructiveHint=false, openWorldHint=true), so the description's main additions are cost and provenance: '$0.02 USDC per call' and 'Source: DeepDAO public data'. Those are genuinely useful for an agent deciding whether to spend a paid call, but the description says nothing about freshness, pagination, coverage limits, or whether results are a ranked list versus aggregate medians.

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?

Four short clauses, front-loaded with the subject and metric list, then supporting facts (median values, source, price). Dense with no filler, though the embedded sample statistics ('$550M treasury, 61% stablecoin, 48-month runway') sit awkwardly between the capability statement and the cost note.

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?

For a simple two-optional-parameter benchmark lookup with no output schema, the description does the heavy lifting by describing what the return contains (top DAOs ranked across four metrics plus median benchmarks). The remaining gap is whether the output mixes a ranked list with aggregate medians, and the absence of any parameter guidance.

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 0% for two optional parameters, so the description must compensate. It partially does: naming 'top DAOs by treasury size, stablecoin percentage' implicitly maps to the sort_by enum values, but min_treasury_usd is never mentioned and the enum's exact spellings ('treasury', 'stablecoin_pct') are not echoed. A caller still has to read the schema to know how to filter or sort.

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 metrics covered: treasury size, stablecoin percentage, runway, and governance token concentration. It doesn't explicitly contrast itself with sibling benchmark tools, but the subject matter is unambiguous enough that an agent can distinguish it by topic alone.

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 when-to-use guidance, no mention of when this is inappropriate, and no routing to alternatives. The agent must infer that this is a read-only lookup for DAO treasury comparisons purely from the noun phrase, with no exclusions or preconditions 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