FortFi Treasury MCP

list_wallets

List FortFi wallets for this account: chain, address, nickname, metadata tags, and default flag. Optional metadataKey/metadataValue filter (exact match). Pass cursor and/or limit to page through large fleets — response becomes { items, nextCursor } when either is set; omit both for the plain array of all wallets.

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": "list_wallets"
  }
}

Input Schema

Name	Required	Description
`limit`	No	Page size when paginating (default 50, max 200)
`cursor`	No	Opaque cursor from a previous page's nextCursor. Passing this (even empty) switches the response to { items, nextCursor }.
`metadataKey`	No	Filter wallets that include this metadata key (optional)
`metadataValue`	No	When set with metadataKey, require an exact value match

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 3, 2026

TDQS

A4.3/5.0

Behavior4/5

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

With no annotations supplied, the description carries the full behavioral burden and does disclose a genuinely non-obvious trait: the response shape changes to { items, nextCursor } when cursor or limit is set, versus a plain array otherwise. It does not mention permission/scope requirements or any limits on total result size, so it is strong but not exhaustive.

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

Conciseness5/5

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

Two sentences, front-loaded with the resource and returned fields, then the optional filter, then pagination. Every clause carries information an agent needs; nothing is padding.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

A simple read-only list tool with no output schema, and the description compensates by naming the returned fields and explaining the two possible response shapes. Nothing essential to invoking it correctly is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so all four parameters are already documented, including defaults, max page size, and the cursor's response-shape effect. The description's parameter statements ('exact match' filtering, cursor/limit switching the response) largely restate the schema, adding framing rather than new semantics — the baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('List FortFi wallets'), scopes it ('for this account'), and enumerates the returned fields (chain, address, nickname, metadata tags, default flag). An agent knows exactly what comes back without another call, and no sibling tool in the list is a plain wallet lister, so the ambiguity risk is low.

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?

Gives concrete guidance on when to paginate ('Pass cursor and/or limit to page through large fleets') and when not to ('omit both for the plain array of all wallets'), plus when to use the metadata filter (exact match). It stops short of naming an alternative tool or stating prerequisites, which keeps it from a 5.

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

All FortFi Treasury MCP tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?