Skip to main content
Glama
Sign In

L2WS

by com.l2ws
OverviewDiscussionsAdmin

save_strategy

Save a strategy (the contract is in get_contract_docs). Returns strategy_id, version and the lint result.

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": {
      "name": "<name>",
      "code": "<code>"
    },
    "name": "save_strategy"
  }
}

Input Schema

NameRequiredDescriptionDefault
codeYes
nameYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.1/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full behavioral-disclosure burden. It usefully states that the result includes strategy_id, version, and lint result, but it omits save semantics such as overwrite behavior, permissions, idempotency, and what happens when lint fails.

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 two compact sentences, front-loads the action, and includes only the doc pointer and return fields. There is no unnecessary wording.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple two-parameter tool, the description covers purpose, documentation location, and return fields. Still, with no output schema and no annotations, it leaves parameter semantics and mutation behavior too implicit.

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

Parameters2/5

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

Schema description coverage is 0%, and the description does not explain the two parameters beyond their schema titles. The get_contract_docs pointer hints at the expected code contract, but it does not define name/code meaning or format directly.

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 verb and resource: "Save a strategy." It clearly separates this from read/list tools, though it does not explicitly clarify create-vs-update or contrast with nearby siblings.

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 parenthetical points to get_contract_docs as the source of the contract, which is a useful prerequisite. However, it gives no explicit when-to-use guidance, when-not-to-use conditions, or alternatives for validating versus saving.

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

All L2WS 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