Skip to main content
Glama

scaffold_component

Scaffolds a strategy component stub for entry, exit, risk, sizer, or strategy, giving coding agents a framework-correct template to add trading logic.

Instructions

Write a framework-correct scaffold for a strategy component file.

    Produces a minimal stub that matches echolon's loader contract —
    class name + method signature + return schema — but contains no
    trading logic. Coding agents refine the stub into real pathways.

    Args:
        kind: One of ``"entry"``, ``"exit"``, ``"risk"``, ``"sizer"``, ``"strategy"``.
        strategy_dir: Absolute path to the directory where the file is written.
        force: If True, overwrite an existing file. If False (default), refuse
            and return ``success=False`` with ``error="file_exists"``.

    Returns:
        {
            "success": bool,
            "output_path": str (path to the scaffolded file, if success),
            "kind": str (echoes the input),
            "error": str | None (one of: "unknown_kind", "file_exists", None),
            "message": str (human-readable summary),
        }
    

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
kindYes
strategy_dirYes
forceNo
Behavior4/5

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

No annotations provided, so description must disclose behavior. It explains file writing, overwrite control via force, stub nature (no trading logic), and return schema. Does not mention permissions but this is acceptable for a file-writing tool.

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?

Description is well-organized with clear sections for purpose, args, and returns. Uses concise language without redundancy. Every sentence adds value.

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?

Despite no output schema, description provides full return schema. All parameters and behavior (including error cases) are covered. Complete for a file generation tool with the given context signals.

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?

Schema description coverage is 0%, but description fully explains each parameter: kind with allowed values, strategy_dir as absolute path, force overwrite behavior. Also details return schema. Provides meaning beyond raw 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?

Description clearly states it writes a scaffold stub for strategy components with class name, method signature, and return schema. It is distinct from sibling tools which are validation and listing utilities.

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?

States that coding agents refine the stub into real pathways, indicating its use as a template generator. No explicit when-not-to-use guidance, but context is clear given sibling tools are not generation-focused.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/DolphinQuant/echolon'

If you have feedback or need assistance with the MCP directory API, please join our Discord server