FortFi Treasury MCP

remove_cosigner

Remove an active co-signer from this account. GOVERN action (it shrinks the approver set): via an agent key, sign a challenge with your funding wallet (challengeId + walletSignature); applies immediately once signed.

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": {
      "membershipId": "<membershipId>"
    },
    "name": "remove_cosigner"
  }
}

Input Schema

Name	Required	Description
`challengeId`	No	Governance challengeId from the first call
`membershipId`	Yes	Membership id from list_cosigner_memberships
`walletSignature`	No	Funding-wallet signature over the challenge message

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 3, 2026

TDQS

A4/5.0

Behavior4/5

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

With no annotations, the description carries the behavioral disclosure and does so well: it states that this is a governance mutation, shrinks the approver set, requires signing a challenge with the funding wallet, and applies immediately once signed. It stops short of explaining reversibility, side effects on pending approvals, or failure behavior.

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?

The description is two compact sentences with the purpose and governance-impact warning front-loaded, followed by the signing requirement. Every clause contributes useful information without 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 three-parameter mutation with no annotations or output schema, the description covers the essential purpose, authorization flow, and immediate effect. It could be more complete by noting prerequisites such as needing an active membership or how pending governance requests are affected.

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 description coverage is 100%, and the schema already documents membershipId, challengeId, and walletSignature. The description reinforces that challengeId and walletSignature work together as a signing flow, but adds limited meaning beyond the schema.

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?

The description names a specific verb and resource: 'Remove an active co-signer from this account.' The qualifier 'active' distinguishes it from invite- or pending-related siblings, so an agent can identify the operation without opening the schema.

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 establishes that this is a governance action that shrinks the approver set, which implies when it applies. However, it does not name alternatives or state when not to use it, such as revoking an invite versus removing an active co-signer.

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?