sa-ecosystem-node

Ecosystem Fund limit

ecofund_limit

Read-onlyIdempotent

Calculates PIP-23 Ecosystem Fund refills, the 5% limit, next-quarter projection, and remaining ATLAS after caller-supplied unpaid PIPs, with an optional labeled Council override.

Instructions

PIP-23 Ecosystem Fund refills, the 5% limit, the next-quarter projection, and remaining ATLAS after caller-supplied unpaid PIPs. Unknown where PIP-23 states no rule. An optional Council override is labelled and does not replace the computed figure. If the cache file is not in this deployment yet, the result says the cache is not yet populated and includes no figures. 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": "ecofund_limit"
  }
}

Input Schema

Name	Required	Description
`asOf`	No	ISO timestamp used to pick the next quarter date. Defaults to the cached balance time.
`unpaidPips`	No	Council-supplied unpaid amounts in ATLAS. Omit the field to leave remaining unknown. An empty list means the caller says there are none.
`councilOverride`	No	Labelled Council figure. Shown beside the computed limit, not silently substituted.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Nov 4, 2026

TDQS

A3.5/5.0

Behavior4/5

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

Annotations already declare read-only, idempotent, and non-destructive behavior, but the description adds useful operational context: unknown where PIP-23 states no rule, override figures are labelled rather than substituted, and an unpopulated cache yields no figures. It does not cover return shape or more subtle failure modes, but it meaningfully extends the annotation profile.

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

Conciseness3/5

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

The description is compact but dense and front-loaded with a compressed noun list rather than a clear action statement. Most sentences carry useful information, though repeating "Read-only" adds little beyond the annotations.

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 read-only calculation tool with three optional parameters and no output schema, the definition explains the key edge cases: unknown results when no rule exists, labeled overrides, and empty cache behavior. It could be more complete about the returned figure structure, but the critical calling behavior is covered.

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?

Schema coverage is 100%, so the baseline is 3. The description adds cross-parameter meaning beyond the schema, especially that unpaid PIPs are caller-supplied and affect remaining ATLAS, and that a Council override is labelled without replacing the computed figure.

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 states a specific computed resource: PIP-23 Ecosystem Fund refills, the 5% limit, next-quarter projection, and remaining ATLAS after unpaid PIPs. It does not explicitly differentiate itself from treasury- or PIP-related siblings, but the calculation purpose is clear enough to identify the tool.

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?

The description gives no explicit when-to-use guidance, exclusions, or named alternatives such as dao_treasury_flows or pip_tracker. An agent can infer that it is for computing the fund limit, but not when to choose it over the sibling tools.

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