Skip to main content
Glama

AINDEX

Collect what a discontinued pooled Fund owes

fund_claim
Read-only

Funds are discontinued; this is only for someone still holding shares in a pooled Fund. The unsigned transactions that collect what settlements priced for a holder: shares from deposits and USDC from redemptions, every claimable batch at once (or one epoch). Anyone may send a claim; what it pays always goes to the holder.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "fund": "<fund>",
      "owner": "<owner>"
    },
    "name": "fund_claim"
  }
}

Input Schema

NameRequiredDescriptionDefault
fundYes
epochNo
ownerYesThe holder

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, and the description stays consistent with that: it returns unsigned transactions rather than executing anything, so nothing is mutated server-side. It also adds two things annotations cannot convey — the claim is permissionless ('anyone may send a claim') and proceeds are non-custodial ('always goes to the holder'). It omits gas/native-token requirements and what happens when nothing is claimable.

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?

Roughly three sentences, front-loaded with the eligibility precondition before describing the payload and payout. The middle sentence is a fragment ('The unsigned transactions that collect what settlements priced for a holder: ...') that takes a second read, but no sentence is filler.

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?

No output schema exists, and the description correctly supplies the return shape — unsigned transactions — plus the payout destination and scope control. For a three-parameter tool this is nearly sufficient, with only edge-case behavior (no claimable amount, signing/sending steps) left implicit.

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 only 33%, with just 'owner' described as 'The holder', so the description must carry weight and does: it identifies 'fund' as the discontinued pooled Fund and explains that omitting 'epoch' claims every claimable batch at once. That resolves the optionality of 'epoch' far better than the schema's bare minimum:1.

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 verb and resource: collect what a discontinued pooled Fund owes a holder, paying out deposit shares and redemption USDC. The 'discontinued' precondition implicitly scopes it away from other fund tools, but no sibling such as fund_redeem is named, so the differentiation is inferred rather than stated.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

'This is only for someone still holding shares in a pooled Fund' gives a clear eligibility condition for use, and '(or one epoch)' clarifies the all-batches-vs-single-epoch choice. There is no explicit when-not-to-use or named alternative for live funds.

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