Skip to main content
Glama

AINDEX

Leave a discontinued pooled Fund

fund_redeem
Read-only

Funds are discontinued; this is only for someone still holding shares in a pooled Fund. The unsigned transaction that asks the Fund to buy back shares (a number of shares, or "all"), or takes back a request still in the open batch (cancel: true, with epoch). Priced at a later settlement; claim the USDC with fund_claim. For the holder's own wallet to sign; AINDEX sends nothing.

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>",
      "from": "<from>"
    },
    "name": "fund_redeem"
  }
}

Input Schema

NameRequiredDescriptionDefault
fromYesThe holder
fundYes
epochNoThe batch of the request to take back; every one that can be, when left out
cancelNoTake back a deposit or redemption request instead
sharesNoShares to redeem, or "all"

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior3/5

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

The annotations declare readOnlyHint=true and openWorldHint=false, which loosely hold for a tool that only builds a transaction. Beyond those annotations, the description adds useful behavior: the transaction is unsigned, the holder's wallet must sign it, AINDEX sends nothing, and pricing occurs at a later settlement. What remains undisclosed is how the returned transaction is delivered and whether there is any expiration, so it lands at 3.

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 sentences, front-loaded with the discontinuation caveat, and every clause carries information about purpose, settlement, or follow-up. The second sentence is an awkward fragment, and "cancel: true" is sloppy shorthand, but there is no padding or repetition.

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 5-parameter tool with no output schema, the description covers enough: the return is an unsigned transaction, the holder signs it, settlement is later, and fund_claim completes the flow. Documentation of the exact response shape or batch mechanics would make it fully complete, but nothing essential for a correct call is missing.

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 80%, so the schema already explains most parameters. The description still clarifies the shares parameter: a number of shares, or "all". It also ties epoch to cancel. The shorthand "cancel: true" conflicts with the schema, which declares cancel as an enum of "deposit" or "redeem", which is a real imprecision.

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 action with its resource: an unsigned transaction that asks the Fund to buy back shares, or takes back an open-batch request. It sets clear scope ("Funds are discontinued; this is only for someone still holding shares"), and it distinguishes this tool from fund_claim. The dense wording, especially the fragment "The unsigned transaction that asks...", keeps it just short of a model 5.

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?

The description gives solid usage context: only for holders of a discontinued pooled Fund, cancel via cancel plus epoch instead of redeeming, and use fund_claim afterward to collect USDC. It does not state explicit exclusions for non-holders beyond "only for someone still holding shares", but no alternative sibling is wrongly suggested.

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