Skip to main content
Glama

Strategy rule compiler

submit_strategy_rule_compiler
Idempotent

Compile plain-language strategy rules into a structured rule set and a test module, flagging rules that cannot be compiled. When a strategy described in words must become a structured rule set. Do not choose this when the strategy must be executed or backtested. Example requests: Compile these trading rules into a rule set. | Turn this strategy description into structured rules. | Check whether these rules are implementable.

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": {
      "inputs": "<inputs>",
      "authorized_by": "<authorized_by>"
    },
    "name": "submit_strategy_rule_compiler"
  }
}

Input Schema

NameRequiredDescriptionDefault
inputsYes
quote_idNoThe quote_id returned by POST /v1/jobs. Required to authorize a priced capability; the service rejects a priced job that does not name the quote it issued.
authorized_byYesIdentifier of the human or agent authorizing this job.
accepted_priceNoThe amount accepted, exactly as quoted (for example "5.00" or 5). Checked against the stored quote, so a price that moved between quote and authorize is refused rather than silently absorbed. Optional, but sent to make the acceptance explicit.

Output Schema

NameRequiredDescriptionDefault
quoteNo
stateYes
job_idYes
artifactsNo
access_tokenNoPer-job credential. Present it as the X-Job-Token header to read the job or list it. Keep it; it is the only credential for this job.
verificationNoIndependent verification. verification.ok = false means the job failed, not a partial success.
capability_idNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare mutation behavior (readOnlyHint=false), idempotency, non-destructiveness, and closed-world scope. The description adds useful context by stating it produces a test module and flags rules that cannot be compiled, which goes beyond the annotations. It does not mention pricing/quote requirements or async job submission, which are covered in the schema.

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 front-loaded with the core purpose, followed by usage guidance, exclusion, and example requests. Every sentence earns its place with no redundant or ambiguous wording.

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?

The description is mostly complete for a job-submission tool with an output schema: purpose, usage, exclusion, and examples are present. It omits explicit mention of pricing/authorization requirements, but those are well-covered in the input schema descriptions and annotations, so the gap is minor.

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

Parameters3/5

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

Schema description coverage is 75% (high), so the schema already documents most parameters including nested rules/indicators and quote_id authorization. The description adds no additional meaning beyond the schema for any parameter, making a baseline 3 appropriate when schema does the heavy lifting.

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?

The description states a specific verb (compile) and resource (plain-language strategy rules into a structured rule set and test module), and explicitly distinguishes the tool from execution/backtesting. An agent can immediately tell what this tool does and what it does not do.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides clear when-to-use guidance ('When a strategy described in words must become a structured rule set') and an explicit exclusion ('Do not choose this when the strategy must be executed or backtested'). It lacks naming a specific alternative sibling tool, but the usage context is well-defined and supported by example requests.

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