Skip to main content
Glama

Create, edit or refine a saved Gambit

save_mandate
Destructive

Create, edit, pause or refine one of YOUR saved Gambits (mandates: standing instructions that tell Gambit what to watch for you; requires api:account). Pick the action. create: a new saved Gambit from title and mandate_text (your own words); status draft (default) or active. update (mandate_id): a draft's content can change in place; status moves draft → active, active → paused (pause), paused → active (resume); monitor_interval_minutes may change at any time. An active or paused saved Gambit is never edited in place: supersede (mandate_id) drafts a successor with your changed fields, then update the successor to status active, which replaces the original. refine: turns loose intent (text) into a suggested title and wording; nothing is saved — pass the result to create. compile_scope: previews which instruments a list of universe terms (terms) resolves to; nothing is saved. autonomy_level 0-3 only: execution autonomy (level 4 and above) can be set only in the Gambit app, and an API key cannot activate, edit or supersede a saved Gambit that holds it (it can still pause one). Your plan limits how many saved Gambits you keep (drafts and paused ones count); over the limit the call answers 403 with code tier_limit_exceeded. A refused lifecycle rule answers 422 with code mandate_rule_violation and reasons, fixed codes naming the rule (e.g. active_mandate_immutable:title — edit through supersede; invalid_transition:draft->paused). Nothing here places a trade. To stop one, pause it (update with status paused). create, update and supersede return the saved Gambit (the same fields as a list_mandates row) and carry app_url, the screen where saved Gambits are managed.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "action": "<action>"
    },
    "name": "save_mandate"
  }
}

Input Schema

NameRequiredDescriptionDefault
textNoREQUIRED for refine: the loose intent to refine
termsNoREQUIRED for compile_scope
titleNoREQUIRED for create
actionYes
statusNocreate: draft | active; update: draft | active | paused; not for supersede
metadataNo
starts_atNo
expires_atNo
mandate_idNoREQUIRED for update and supersede
mandate_textNoREQUIRED for create: the instruction, in the user's words
policy_deltaNorisk bounds and preferences for this saved Gambit
autonomy_levelNo
monitor_interval_minutesNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.8/5.0
Behavior5/5

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

Annotations declare destructiveHint=true and readOnlyHint=false, but the description adds far more than the safety flag: the api:account scope requirement, the active_mandate_immutable rule with sample 422 codes, the tier_limit_exceeded 403 on plan caps, whether drafts and paused Gambits count toward the limit, the API-key restriction on activating edits, and the explicit statement that nothing places a trade and pausing is the way to stop one. This is exactly the behavioral context annotations cannot carry.

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?

The description is a single dense block but is front-loaded with the action menu, followed by constraints and then error semantics. Nearly every clause carries operational information; only the app_url sentence at the end could be trimmed because the response shape is already described.

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?

With 13 parameters, nested objects, and no output schema, the description still covers return values ('the same fields as a list_mandates row' plus app_url) and the failure modes. An agent has enough to select the action, satisfy required fields, and anticipate 403/422 outcomes.

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?

Schema coverage is 54% across 13 parameters, so the description has to compensate and largely does: it explains what text, terms, title, mandate_text, mandate_id, status, and autonomy_level do in each action, and clarifies status transitions that the enum alone does not. It leaves metadata, starts_at, expires_at, and policy_delta unexplained beyond the bare schema, which keeps it below a 5.

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 set (create, edit, pause, refine) against a named resource (saved Gambits / mandates), defines the resource parenthetically, and covers five distinct actions. An agent can distinguish it from create_gambit, plan_gambit, and update_gambit_monitoring without opening any schema.

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?

Every action is given an explicit trigger: create from title and mandate_text, update for drafts and status transitions, supersede when the target is active or paused, refine for loose intent with 'nothing is saved — pass the result to create', compile_scope for previewing universe resolution. It also names the exclusion (execution autonomy level 4+ only in the app) rather than leaving it to inference.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources