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

sa-ecosystem-node

by PhoenixClaw01
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Hybrid

Treasury balances

treasury_balances
Read-onlyIdempotent

Fetch live SOL, ATLAS, and USDC balances for the DAO Treasury and Ecosystem Fund, with cached fallback and read-only Squads v3 multisig decoding.

Instructions

Live SOL, ATLAS, and USDC balances for the DAO Treasury and Ecosystem Fund from one getMultipleAccounts read, with the treasury cache as fallback. Includes a read-only Squads v3 decode of the two published multisigs when the live read works. Standard token accounts only. 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": "treasury_balances"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive, so the description's added value is in the data mechanics: one getMultipleAccounts read, treasury cache as fallback, and the multisig decode only succeeding 'when the live read works'. The 'Standard token accounts only' caveat usefully flags a scope limit that would otherwise cause silent omissions.

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 compact sentences, front-loaded with what the tool returns, then sourcing behavior, then scope caveat. Dense Solana jargon ('getMultipleAccounts', 'Squads v3 decode') is justified for the audience but is information the agent cannot act on, keeping it just below top marks.

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 parameters and no output schema, the description carries the burden of describing what comes back, and it does name the assets, the two accounts, the fallback path, and the optional multisig decode. Return shape (field names, per-account structure) remains underspecified, which is the main residual gap.

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 tool takes zero parameters, so there is no per-parameter meaning to add and the baseline applies. Nothing in the description misleads about inputs.

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?

States a specific resource (live SOL/ATLAS/USDC balances) and scope (DAO Treasury and Ecosystem Fund), which implicitly separates it from flow/history siblings like treasury_history and dao_treasury_flows. It stops short of naming an alternative outright, so an agent must infer the boundary rather than being told it.

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?

The description implies the use case is 'current snapshot balances' versus historical flows, but never says when to prefer this over treasury_history or dao_overview. No prerequisites or exclusions are stated; the only usage constraint is the implicit 'standard token accounts only'.

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