Skip to main content
Glama

dMoERA Creator

by io.github.CacheCarti

get_market_regime

Get current market regime classification.

Returns the aggregate regime (e.g. "bull_calm", "bear_volatile"),
per-symbol regimes, crisis score, and the derivatives data driving
the classification (funding rates, open interest, long/short ratios,
taker buy/sell ratios).

Regime determines which trade directions are allowed:
- bull_* → longs only
- bear_* → shorts only
- neutral_* → both longs and shorts
- crisis/meltdown → no new positions

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

TDQS

A4/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full burden. 'Get' implies a read-only operation, and the description covers output contents well, but it does not disclose whether the data is live or cached, whether authentication or initialization is required, or any other behavioral caveats. Acceptable for a zero-parameter getter but not thorough.

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 compact and front-loaded with purpose. Each subsequent line adds interpretive value, whether listing output fields or mapping regime values to allowed trade directions. No wasted words.

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?

With no parameters, an output schema, and a simple read operation, the description covers the core semantics and return-value interpretation. The missing piece is an explicit statement of when to call it (e.g., 'call this before opening any position'), though the regime rule lines imply that timing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool has zero parameters, so the schema trivially covers everything and the description has no parameter information to add. Baseline 4 applies.

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 ('Get'), a clear resource ('current market regime classification'), and enumerates the exact returned data (aggregate/per-symbol regimes, crisis score, and derivatives data). The regime semantics further separate it from the unrelated sibling trading/fund management tools.

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 description does not explicitly name alternatives or when-not-to-use this tool. However, the line 'Regime determines which trade directions are allowed' implies it should be consulted before trading, so usage is conveyed through implication rather than explicit 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