Skip to main content
Glama

dMoERA Creator

by io.github.CacheCarti
OverviewDiscussionsAdmin

create_fund

Create a new personal 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.
Personal funds can ONLY contain the user's own bots — use list_my_bots
to see eligible strategies.

Args:
    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
fund_nameNoMy Hedge Fund
philosophyNo
router_presetNostandard
aggression_modeNonormal

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"
-}
    • removedInput schema / required
      Removed value: -[
-  "user_id"
-]
  2. Added

TDQS

A4.6/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 full burden and does well: it discloses the inactive initial state, the wallet_cash deduction at creation, and the restriction that personal funds can only contain the user's own bots. It lacks some details like error conditions, but covers the most important behavioral traits.

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 front-loaded with the core purpose, then briefly covers behavioral constraintsaic, then enumerates parameters in a compact list. Every sentence adds value, and the Args block is neatly structured without redundancy.

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 complexityhra, the description covers prerequisites (wallet_cash, eligible bots), post-creation steps (activate_fund), parameter constraints, and return value. The presence of an output schema means the return-object explanation is sufficient, and no critical context appears missing.

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, but the description fully compensates by documenting every parameter: fund_name as display name, router_preset with its four allowed values, aggression_mode with its two values, and philosophy with optionality and max length. This is more semantic detail than typical schema descriptions provide.

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 ('Create') and resource ('personal hedge fund') scoped to 'the authenticated user', immediately distinguishing it from sibling fund-related tools like activate_fund and close_fund. The description clearly identifies what the tool produces.

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 contextual guidance: the fund starts inactive and requires activate_fund for Manager Mode, initial capital comes from wallet_cash, and eligible bots are found via list_my_bots. It doesn't explicitly state when not to use this tool or name alternatives, but the guidance is actionable and distinct.

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