Skip to main content
Glama

dMoERA Creator

by io.github.CacheCarti

activate_fund

Activate Manager Mode for a fund — starts the personal router.

This deploys capital across the fund's roster bots according to their
weights and the fund's risk caps. The main platform router is paused
while Manager Mode is active.

Args:
    user_id: The user's ID (must own the fund).
    fund_id: The fund's ID.

Returns success or error.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
fund_idYes
user_idYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

TDQS

A3.9/5.0
Behavior4/5

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

With no annotations provided, the description carries the behavioral disclosure burden. It does well by stating that this starts the personal router, deploys capital according to weights and risk caps, and pauses the main platform router while active. It also adds the ownership requirement for user_id, though it could say more about reversibility or error cases.

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?

The description is appropriately sized and front-loaded with the core purpose. Every sentence contributes meaning, including side effects and argument ownership. The 'Returns success or error' line is slightly redundant given the output schema exists, but it is compact and not harmful.

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 fund activation tool with no annotations and an output schema, the description covers the essential behavioral context: what starts, what gets paused, how capital is deployed, and the ownership constraint. It lacks explicit guidance on deactivation or interactions with sibling tools, but it is largely complete for invoking this tool correctly.

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 0%, so the description must compensate. It provides brief semantic meaning for both parameters: user_id is the user's ID and must own the fund, and fund_id is the fund's ID. This is useful but minimal, and does not add much beyond what the schema's names and types already suggest.

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 specific verb and resource: 'Activate Manager Mode for a fund — starts the personal router.' It clearly differentiates this from sibling tools like deactivate_fund or close_fund by naming the exact action and its effect.

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 context of when to use this tool is implied through the behavior described: deploying capital and pausing the main platform router while Manager Mode is active. However, it does not explicitly mention alternatives like deactivate_fund or state when not to use it, leaving some routing to inference.

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