FortFi Treasury MCP

remove_backup_governance_wallet

Remove the registered backup governance wallet. GOVERN action: sign with your funding wallet (challengeId + walletSignature); applies immediately once signed. After removal, only the funding wallet may authorize governance.

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

Input Schema

Name	Required	Description	Default
`challengeId`	No	Governance challengeId from the first call
`walletSignature`	No	Funding-wallet signature over the challenge message

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, the description carries the full burden and does well: it discloses the auth model (funding-wallet signature over a challenge), that the change applies immediately upon signing, and the downstream consequence that only the funding wallet can authorize governance afterwards. It omits edge behavior such as what happens when no backup wallet is registered or whether the action needs prior approval.

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?

Three short sentences, front-loaded with the operation and followed by the signing requirement and the resulting state change. Minor redundancy in restating the two parameter names, but no wasted prose.

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 two-parameter governance mutation with no output schema and no annotations, the description covers purpose, auth, immediacy, and the post-removal permission state. Gaps are limited to preconditions (must a backup wallet exist / must it be registered first) and the response shape.

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 both parameters are already documented in the schema. The description only places challengeId and walletSignature in the signing flow, adding workflow context but no format or value semantics beyond the schema — the baseline 3 applies.

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 (remove) and resource (the registered backup governance wallet), which cleanly inverts the sibling register_backup_governance_wallet. It does not explicitly name that sibling, but the resource framing makes the pairing unambiguous.

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 description supplies prerequisites (must be a GOVERN action signed by the funding wallet, using challengeId + walletSignature) rather than an explicit when-to-use versus when-not-to-use rule. There is no stated alternative or condition beyond the signing requirement, so usage is implied rather than guided.

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?