Skip to main content
Glama
Sign In
sa-ecosystem-node

sa-ecosystem-node

by PhoenixClaw01
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Hybrid

DAO treasury flows

dao_treasury_flows
Read-onlyIdempotent

Retrieves monthly DAO Treasury and Ecosystem Fund inflows and outflows from the local signature cache, with optional partial rows when cache support is incomplete. Read-only.

Instructions

Monthly inflows and outflows for the DAO Treasury and Ecosystem Fund, from the local signature cache. Treasury ATLAS inflows are withheld when the cache cannot support them. Read-only.

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

Input Schema

NameRequiredDescriptionDefault
toNo
fromNo
mintNoATLAS, USDC, or SOL.
walletNodao_treasury, ecosystem_fund, or one of those two published addresses.
allowPartialNoInclude rows the cache cannot fully support. Default false.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnlyHint, idempotentHint, destructiveHint=false), so the bar is lower, and the description still adds genuinely useful behavior: the data source is the local signature cache and Treasury ATLAS inflows are suppressed when the cache cannot support them. That withholding rule is a non-obvious limitation the agent would otherwise miss. It stops short of saying how partial results are surfaced or how the allowPartial flag changes the output.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three short sentences with no filler: scope first, then the data source and its limitation, then the read-only property. Nothing redundant and nothing buried.

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 five-parameter, all-optional read tool with no output schema, the description covers what is returned (monthly flows), for which wallets, from which source, and the main caveat. The remaining gaps, such as how from/to bound the range and what a partial row looks like, are modest.

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 coverage is 60%: mint and wallet carry enumerated descriptions and allowPartial explains its default, while from/to expose only a YYYY-MM pattern with no prose. The description adds meaning for allowPartial by explaining that unsupported rows are withheld unless partial results are requested, but it does not clarify the from/to range semantics or the month boundary behavior.

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 metric (monthly inflows and outflows) and a specific resource (DAO Treasury and Ecosystem Fund), which is far more informative than the title alone. It distinguishes itself implicitly from siblings such as treasury_balances or treasury_history by emphasizing flows and monthly aggregation, but it never names those alternatives explicitly.

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 explicit when-to-use or when-not-to-use guidance; nothing tells the agent to prefer dao_revenue, dao_payments, or treasury_history in any situation. The only usable hints are implied: the data comes from a local signature cache and some data may be withheld, which the agent must infer means results are best-effort.

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

Deploy Server

Other Tools