Skip to main content
Glama

dMoERA Creator

by io.github.CacheCarti

create_fund

Create a new hedge fund for the user.

The fund starts inactive — call activate_fund to start Manager Mode.
Initial capital is taken from the user's wallet_cash at creation time.

Args:
    user_id: The user's ID.
    fund_name: Display name for the fund.
    router_preset: Risk profile — one of "prudent", "standard",
                  "opportunistic", "unrestricted".
    aggression_mode: "normal" or "yolo".
    philosophy: Optional text describing the fund's investment thesis
               (max 2000 chars).

Returns the created fund object.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
user_idYes
fund_nameNoMy Hedge Fund
philosophyNo
router_presetNostandard
aggression_modeNonormal

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

TDQS

A4.8/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 burden of disclosing behavior. It does so well by stating that the fund is created inactive, that initial capital is deducted from wallet_cash, and that the created fund object is returned. This goes beyond the schema and gives the agent useful behavioral expectations, though it could also mention side effects such as capital deduction irreversibility or possible failure conditions.

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 with a brief summary, bullets for Args, and a return statement. Every sentence adds value, and the most important behavioral details (inactive state, capital source, activation path) are front-loaded. No filler or redundant content.

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?

For a creation tool with no annotations and low schema coverage, the description provides a complete picture: what it does, key side effects, parameter semantics, and return value. The output schema exists, so return details need not be exhaustive. The description is fully sufficient for an agent to correctly select and invoke this tool.

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?

The input schema has 0% description coverage, so the description must compensate. It does, explaining all five parameters: user_id, fund_name, router_preset with allowed values, aggression_mode with allowed values, and philosophy with a max length. This is exactly the kind of semantic enrichment the schema lacks.

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 states a specific verb and resource: 'Create a new hedge fund for the user.' It clearly differentiates from the sibling activate_fund by explaining that the fund starts inactive and requires activation. This makes the tool's purpose unmistakable.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description explicitly says the fund starts inactive and directs the agent to call activate_fund to start Manager Mode. It also notes that initial capital is taken from wallet_cash, giving important context for when this tool should be invoked. This provides clear usage guidance relative to the sibling activation tool.

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