Skip to main content
Glama

dMoERA Creator

by io.github.CacheCarti
OverviewDiscussionsAdmin

swap_bot_in_fund

Swap one bot for another in a fund's roster.

Closes the old bot's positions and opens new ones for the replacement.
Incurs friction cost — use estimate_swap_cost first.

Args:
    fund_id: The fund's ID.
    old_bot_id: The bot to remove.
    new_bot_id: The bot to add in its place.
    new_bot_domain: The new bot's domain (e.g. "eth_usdc").
    weight: Allocation weight for the new bot (defaults to old bot's weight).
    reason: Optional reason for the swap.

Returns the updated roster entry and friction estimate.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
reasonNo
weightNo
fund_idYes
new_bot_idYes
old_bot_idYes
new_bot_domainYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • removedInput schema / properties / user_id
      Removed value: -{
-  "title": "User Id",
-  "type": "string"
-}
    • changedInput schema / required
      Previous value: -[
-  "user_id",
-  "fund_id",
-  "old_bot_id",
-  "new_bot_id",
-  "new_bot_domain"
-]New value: +[
+  "fund_id",
+  "old_bot_id",
+  "new_bot_id",
+  "new_bot_domain"
+]
  2. Added

TDQS

A4.8/5.0
Behavior5/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It states the side effects (closes old bot's positions, opens new ones), the associated cost (friction), and the return value (updated roster entry and friction estimate). This is comprehensive and honest about the tool's mutation 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 well-structured: a clear purpose statement, a sentence on side effects and cost, then a list of parameters. The parameter documentation is justified given the 0% schema coverage, and every sentence adds value without verbosity. It is front-loaded with the most critical information.

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?

Given the tool's complexity (6 parameters, no annotations, 0% schema coverage) and the presence of an output schema (not shown but flagged as true), the description covers all necessary ground: it explains the prerequisite, the behavioral effect, the parameters, and the return type. An agent would have everything needed to invoke it correctly.

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

Parameters5/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. It does so with a dedicated 'Args' section that explains each parameter's role, including defaults (weight defaults to old bot's weight) and optionality (reason). This adds meaningful meaning beyond the bare type declarations in 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 opens with a precise verb-object phrase, 'Swap one bot for another in a fund's roster,' and immediately explains the operational effect (closes old positions, opens new ones). This clearly distinguishes it from sibling tools like add_bot_to_fund or remove_bot_from_fund, leaving no ambiguity about what the tool does.

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?

The description gives an explicit prerequisite: 'use estimate_swap_cost first.' This is actionable guidance that tells the agent when to call a different tool before this one. It does not explicitly list alternatives or when-not-to-use conditions, but the strong contextual clue is sufficient for an agent to route correctly.

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

All dMoERA Creator toolsInspect
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