Skip to main content
Glama

describe_component_api

Retrieve the live API surface of BaseComponent and IMarketData classes for writing component code. Uses inspect.signature to ensure accuracy and avoid documentation drift.

Instructions

Return the live BaseComponent + IMarketData API surface.

    Use this BEFORE writing any component code. The return value is
    produced via ``inspect.signature()`` on the actual classes, so it
    always reflects the current echolon version — there is no skill /
    doc drift. If a method appears here, it exists; if it doesn't, it
    doesn't. Pip-install or editable-install, same answer.

    Returns a dict with shape::

        {
          "BaseComponent": {
            "override_methods": [{"name": ..., "signature": ..., "doc": ...}, ...],
            "helper_methods":   [{...}, ...],
            "properties":       [{"name": ..., "doc": ...}, ...],
          },
          "IMarketData": {
            "methods": [{"name": ..., "signature": ..., "doc": ...}, ...],
          },
        }

    ``override_methods`` are the four BaseComponent stubs each component
    file must override (``generate_signal`` / ``should_exit`` /
    ``can_trade`` / ``calculate_size``). ``helper_methods`` are concrete
    helpers strategies may call (``get_current_bar``, ``get_indicator``,
    ``log_*_output``, etc.). ``properties`` are read-only attribute
    accessors (``self.market_data``, ``self.portfolio``, ``self.params``).

    ``signature`` is the formatted ``inspect.Signature`` (e.g.
    ``"(self, name: str, index: int = 0) -> float"``). ``doc`` is the
    first line of the docstring; full docstrings live on the source.
    

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Behavior5/5

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

Despite no annotations, the description thoroughly explains that the result is produced via inspect.signature() on actual classes, ensuring no drift. It details the return shape and the meaning of each section, providing full behavioral transparency.

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 well-structured with a clear purpose, usage instruction, and detailed return shape. It uses code blocks and bullet points, though some sentences are verbose, earning a 4.

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?

Given no parameters or output schema, the description provides all necessary context: what the tool does, how it works, the return format, and interpretation tips, making it fully complete.

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?

The input schema has no parameters, so schema coverage is 100%. The description adds value by explaining the return value; no parameter details are needed.

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 clearly states the tool returns the live BaseComponent + IMarketData API surface, using specific verbs and resource names. It distinguishes itself from sibling tools like get_doc and list_skills by focusing on the component API surface.

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 explicitly says 'Use this BEFORE writing any component code,' providing clear usage context. However, it does not mention when not to use it or suggest alternatives among sibling tools.

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