Skip to main content
Glama

dMoERA Creator

by io.github.CacheCarti

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:
    user_id: The user's ID (must own the fund).
    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
user_idYes
new_bot_idYes
old_bot_idYes
new_bot_domainYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

TDQS

A4.8/5.0
Behavior5/5

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

No annotations exist, so the description carries full burden. It discloses side effects (closing old positions, opening new ones), a prerequisite (user must own the fund), cost implication (friction), weight default behavior, and the return shape (updated roster entry and friction estimate). This is robust for a mutating tool.

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?

Purpose and behavior are front-loaded in the first line, followed by a brief warning, then a tight Args block and return statement. No filler; every sentence adds information that is not in the schema.

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?

The description covers purpose, side effects, prerequisite, parameter meanings, cost warning, and return value. With an output schema present and all parameters described, nothing essential is missing for an agent to call 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%, yet the description documents all seven parameters with meaningful semantics: ownership requirement for user_id, role of old vs new bot IDs, a domain example, weight defaulting to old bot's weight, and optional reason. This fully compensates for the schema's lack of descriptions.

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?

States a specific verb and resource ('Swap one bot for another in a fund's roster'), describes the mechanism (closes old positions, opens new ones), and naturally distinguishes itself from sibling tools like add_bot_to_fund and remove_bot_from_fund by describing the combined atomic operation.

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?

Provides clear context: the tool is for replacing a bot, and explicitly instructs to 'use estimate_swap_cost first' because it incurs friction cost. It does not explicitly contrast with add/remove alternatives, so it falls just short of full exclusion guidance.

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
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A3.8/5.0
Disambiguation4/5

Most tools target a distinct resource and action, but browse_fund_marketplace and get_marketplace_bots are easy to confuse since both surface marketplace bots with performance metrics. The detailed descriptions clarify their different intents, though the naming does not strongly reinforce the distinction.

Naming Consistency4/5

The set almost uniformly uses snake_case verb_noun names like create_fund, list_funds, and update_fund_weights. Minor inconsistencies exist, such as get_marketplace_bots returning a list instead of a single item and browse_fund_marketplace using a different pattern from the other marketplace tools.

Tool Count3/5

At 26 tools, the server is on the heavy side and above the typical well-scoped range. The broad domain of funds, strategies, marketplaces, and market data helps justify the count, but several overlapping marketplace/list tools inflate the surface and could be consolidated.

Completeness4/5

The set covers the core fund lifecycle, roster management, strategy validation/deployment, marketplace browsing, and market data reads quite thoroughly. Minor gaps remain, such as no update/delete operations for strategies and no direct tool for publishing a bot to the marketplace, but these are workable within the existing workflow.

Resources