Skip to main content
Glama

library_keep

Idempotent

Keep a strategy from the studio library as the trader's own script, its rules exactly as published, so it can be filmed, rehearsed or sent to the gate under its own name. The only change allowed is the glyph each of its states wears on the chart and in a film. Use this, never forge, when the trader names a library strategy: the forge cannot read the library and would write a different rule. Returns the kept name (pass it to film as scripts) and the glyphs it changed.

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": {
      "id": "<id>"
    },
    "name": "library_keep"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesthe library strategy
glyphsNooptional: a glyph per state name (as the script names its states), each one of ◇ ◈ ▣ ■ □ ▲ ▼ ● ○

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / id / enum
      Previous value: -[
      -  "sol-smt-fade",
      -  "btc-smt-fade-1h",
      -  "bear-rally-fade-btc",
      -  "open-range-breakdown-nq",
      -  "ten-day-breakdown-btc",
      -  "liquidity-sweep-eq-btc"
      -]New value: +[
      +  "sol-smt-fade",
      +  "btc-smt-fade-1h",
      +  "bear-rally-fade-btc",
      +  "open-range-breakdown-nq",
      +  "ten-day-breakdown-btc",
      +  "liquidity-sweep-eq-btc",
      +  "swing-runner-ny"
      +]
  2. Added

TDQS

A4.6/5.0
Behavior4/5

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

Goes beyond the annotations by disclosing what the operation preserves (rules exactly as published), what it may change (only per-state glyphs), and what it returns (kept name plus the glyphs it changed). Annotations already cover the safety profile (non-destructive, idempotent, closed-world), so the remaining gap is minor: it does not say what happens on a name collision or whether an existing kept copy is overwritten.

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?

Two dense sentences plus a return-value sentence, front-loaded with the action and the constraint. The house vocabulary ('the gate', 'forge', 'wears on the chart') costs some clarity, but every sentence carries operational information and nothing is padding.

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?

No output schema exists, yet the description names the return values (kept name, changed glyphs) and even explains the downstream handoff to 'film'. Combined with annotations and a fully described two-parameter schema, nothing an agent needs to call this correctly is missing.

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 100%, so the enum of strategy ids and the glyph enum are already documented; baseline would be 3. The description adds meaning by framing glyphs as the sole permitted customization and tying the states to how the script names them, which clarifies intent rather than restating the schema.

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 and resource: copying a named library strategy into the trader's own scripts with rules preserved exactly as published, including the one permitted alteration (glyph per state). It also explicitly distinguishes itself from the sibling 'forge', so an agent can separate the two without inspecting schemas.

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?

Gives an explicit selection rule: use this, never forge, when the trader names a library strategy, with a stated reason (forge cannot read the library and would write a different rule). That is both a when-to-use and a when-not-to-use against a specific alternative.

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