FortFi Treasury MCP

rebalance_strategy_now

Run a strategy's rebalance now instead of waiting for its schedule. Returns the run outcome.

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": {
      "id": "<id>",
      "walletId": "<walletId>"
    },
    "name": "rebalance_strategy_now"
  }
}

Input Schema

Name	Required	Description	Default
`id`	Yes
`walletId`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 3, 2026

TDQS

B3/5.0

Behavior2/5

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

No annotations are supplied, so the description carries the full behavioral burden. It discloses that the tool triggers an immediate rebalance and returns a run outcome, but says nothing about permissions, side effects on funds or positions, reversibility, idempotency, or what happens if the strategy has no schedule.

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 definition is two tight sentences with the immediate-execution purpose front-loaded and no wasted wording. The return-value note is brief but useful in structure.

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

Completeness2/5

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

For a mutation-style operation with no annotations, no output schema, and zero schema parameter coverage, the description is too thin. It leaves out permission requirements, side effects, parameter meanings, and meaningful return details, so an agent lacks enough context to invoke it safely.

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

Parameters2/5

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

Schema description coverage is 0%, so the description must compensate for undocumented parameters. It only implies that 'a strategy's' relates to the id parameter; walletId is entirely unexplained, and neither parameter's format or relationship is clarified.

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 verb and resource: 'Run a strategy's rebalance now.' It also clarifies the timing distinction from the normal schedule. It does not, however, distinguish this tool from nearby siblings such as plan_rebalance or start_strategy.

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 'instead of waiting for its schedule' gives a clear trigger condition for immediate execution. But there is no guidance on when not to use it, no prerequisites, and no explicit comparison with the closely related plan_rebalance or strategy lifecycle tools.

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?