FortFi Treasury MCP

search_vaults

Parent-treasury vault inventory search (treasury credential + keys:manage + wallets:read). Matches nicknames, wallet IDs, addresses, external customer IDs, credential names, and prefixes. Never returns raw bearer keys.

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

Input Schema

Name	Required	Description
`limit`	No	Page size (default 50, max 100)
`query`	No	Free-text search
`cursor`	No	Pagination cursor from prior response
`chainId`	No	Exact chain filter
`metadataKey`	No	Exact metadata key (requires metadataValue)
`metadataValue`	No	Exact metadata value (requires metadataKey)
`credentialAccess`	No	Filter by linked credential access mode
`credentialStatus`	No	Filter by linked credential status
`externalCustomerId`	No	Exact external customer id

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 3, 2026

TDQS

A3.7/5.0

Behavior4/5

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

With no annotations at all, the description carries the full burden and does deliver real behavioral facts: the required credential and scopes, and the security guarantee that raw bearer keys are never returned. It does not state that the call is non-mutating, nor how results are ordered or paged beyond what the schema already shows.

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?

Three short sentences, front-loaded with scope and permission requirements before the matching fields and the security caveat. No filler and no repetition of schema detail.

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?

For a 9-parameter search tool with no output schema and no annotations, the definition covers scope, auth, and match semantics reasonably well. It still leaves the return shape (what a vault record contains, beyond the absence of bearer keys) and pagination behavior unstated.

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 the baseline is 3. The description does add some value by enumerating the fields the free-text 'query' matches (nicknames, wallet IDs, addresses, external customer IDs, credential names, prefixes), which the bare 'Free-text search' schema text does not convey, but it says nothing about chainId, metadata pairing, or the enum filters.

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 — a search over the parent-treasury vault inventory — plus the fields it matches on. It is distinguishable from sibling search_credentials and list_wallets, though it never explicitly names those alternatives.

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?

The phrase 'Parent-treasury vault inventory search' implies when the tool applies and the permission triple (treasury credential + keys:manage + wallets:read) signals prerequisites. However, there is no explicit when-not-to-use guidance or routing to search_credentials or list_wallets, so the agent must infer the boundary.

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?