dMoERA Creator

create_fund

Create a new hedge fund for the authenticated 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:
    fund_name: Display name for the fund.
    router_preset: Risk profile — one of "prudent", "standard",
                  "opportunistic", "unrestricted".
    aggression_mode: "weights" (default — the fund follows your weights
                    exactly; leftover % stays in cash) or "router"
                    (opt-in Kelly sizing; needs bots with a trade history).
    philosophy: Optional text describing the fund's investment thesis
               (max 2000 chars).
    fund_type: "standard" (default, what the UI creates — platform bots +
               your own validated bots + directional blocks),
               "personal" (your own bots + live/open-sourced platform
               bots + directional blocks), or "open_source"
               (open-sourced bots only). Check each bot's fieldable_in
               in list_marketplace_bots before adding.

Returns the created fund object.

Input Schema

Name	Required	Default
`fund_name`	No	My Hedge Fund
`fund_type`	No	standard
`philosophy`	No
`router_preset`	No	standard
`aggression_mode`	No	weights

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 25, 2026
- changedInput schema / properties / fund_type / default
```
Previous value: -"personal"New value: +"standard"
```
Changed1 schema field changedOct 23, 2026
- changedInput schema / properties / aggression_mode / default
```
Previous value: -"normal"New value: +"weights"
```

Changed1 schema field changedOct 23, 2026

addedInput schema / properties / fund_type

Added value: +{
+  "default": "personal",
+  "title": "Fund Type",
+  "type": "string"
+}

Changed2 schema fields changedSep 17, 2026
- removedInput schema / properties / user_id
```
Removed value: -{
-  "title": "User Id",
-  "type": "string"
-}
```
- removedInput schema / required
```
Removed value: -[
-  "user_id"
-]
```
AddedSep 1, 2026

TDQS

A4.4/5.0

Behavior4/5

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

With no annotations, the description carries the full burden and does disclose key behavior: the created entity starts inactive, initial capital is debited from the user's wallet_cash at creation time (a real financial side effect), and it returns the created fund object. It does not mention permission requirements, failure modes (insufficient wallet_cash), or reversibility, which keeps it short of a 5.

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?

Front-loaded with the core action and the activate_fund follow-up before the Args block, which is justified given the zero schema coverage. A few lines are near-redundant ("Display name for the fund"), but overall it is tight for a five-parameter creation tool.

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?

An output schema exists, so "Returns the created fund object" suffices for return values, and the lifecycle plus funding behavior are covered. The only real gap is what to do when wallet_cash is insufficient or when the user already has a fund, which an agent would have to discover by trial.

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 and it does: all five parameters are explained with defaults and enumerated values (router_preset's four risk profiles, aggression_mode's weights vs. router with the Kelly-sizing precondition, fund_type's three variants and their bot composition). This adds meaning well beyond the bare schema titles.

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?

Opens with a specific verb and resource ("Create a new hedge fund") plus the scope ("for the authenticated user"), which separates it cleanly from activate_fund, get_fund, list_funds and the other fund siblings. An agent can identify the operation without opening the schema.

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?

Explicitly states the post-creation lifecycle step ("fund starts inactive — call activate_fund to start Manager Mode") and points at list_marketplace_bots for the fieldable_in check when picking open-source bots. It lacks any when-not-to-use condition (e.g. one fund per user, or existing funds), but the surrounding context is clear.

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

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