sa-ecosystem-node

Data health

data_health

Read-onlyIdempotent

Check freshness and last errors for treasury, galaxy proposals, Council sheet, and wallet balance caches, showing whether balances are live or cached. Read-only diagnostics for spotting stale or failing data.

Instructions

Freshness and the last error for the treasury cache, galaxy proposals, the Council sheet, and wallet balances. Wallet balances say live or cached. 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": "data_health"
  }
}

Input Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Nov 4, 2026

TDQS

A3.5/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, and openWorldHint=true, so the closing 'Read-only.' sentence merely repeats structured data. The description does add genuine behavioral context beyond the annotations: which four subsystems are probed and that wallet balances are flagged live vs cached. It says nothing about how freshness is expressed, how errors are surfaced, or cost/latency of the probe.

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?

Three short sentences with no filler, and the scope enumeration comes first. The final 'Read-only.' sentence is redundant against the annotations and could be cut, which is the only waste.

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?

There is no output schema, so the description carries the burden of describing return values, and it only loosely does so: 'freshness' is undefined (timestamp vs age vs boolean) and 'the last error' gives no shape. For a simple no-parameter diagnostic the coverage is adequate but not sufficient for an agent to know what it will actually receive.

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 parameter meaning for the description to supply and the baseline of 4 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?

The description names the exact resources covered (treasury cache, galaxy proposals, Council sheet, wallet balances) and what is reported for each (freshness and last error), which is far more specific than the title 'Data health'. It stops short of a clean verb-plus-resource framing and never distinguishes itself from siblings such as treasury_balances or list_proposals, which cover overlapping data.

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 only implied: the mention of freshness and last error suggests calling this to verify whether the treasury, proposals, Council sheet, and wallet data are stale before trusting them. There is no explicit when-to-use statement, no statement of when-not-to-use, and no named alternative among the ~21 siblings.

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