Skip to main content
Glama

dMoERA Creator

by io.github.CacheCarti
OverviewDiscussionsAdmin

update_fund_caps

Update a fund's risk caps and settings.

Args:
    fund_id: The fund's ID.
    max_per_bot_pct: Max allocation per single bot (e.g. 40.0 = 40%).
    max_per_domain_pct: Max allocation per domain (e.g. 60.0 = 60%).
    regime_veto_enabled: Whether the regime detector can veto trades.

Only provided fields are updated; others remain unchanged.

Returns success or error.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
fund_idYes
max_per_bot_pctNo
max_per_domain_pctNo
regime_veto_enabledNo

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"
-}
    • changedInput schema / required
      Previous value: -[
-  "user_id",
-  "fund_id"
-]New value: +[
+  "fund_id"
+]
  2. Added

TDQS

A3.9/5.0
Behavior3/5

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

With no annotations, the description carries the behavioral burden. It usefully discloses that 'Only provided fields are updated; others remain unchanged' and that it returns success or error Face, but it does not mention validation rules, permission requirements, or side effects beyond the described update.

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 well-structured: a one-sentence purpose, an Args list covering all parameters, a key behavioral note, and a return statement. No filler or redundant content.

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 simple four-parameter update tool with no annotations, this description covers purpose, argument semantics, partial-update behavior, and return value. It could be more complete with explicit mention of alternatives or edge cases, but nothing critical to invoking it correctly is 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 provides only field names and types with 0% schema description coverageskin. The description fully compensates by explaining each parameter, including units for percentages ('40.0 = 40%') and the meaning of regime_veto_enabled. This is exactly the kind of semantic context an agent needs.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific action and resource: 'Update a fund's risk caps and settings.' It is clear and distinct from nearby tools like update_fund_weights, though it does not explicitly differentiate itself from that sibling.

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?

Usage context is implied by the name and the verb 'Update a fund's risk caps and settings.' There is no explicit guidance about when to prefer this tool over update_fund_weights or other fund-updating siblings, nor any exclusions or prerequisites.

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