Skip to main content
Glama

get_doc

Read any markdown file under echolon/native/ to retrieve its body. Use for skill cross-references, error documentation, or template READMEs not covered by dedicated tools.

Instructions

Read any markdown file under echolon/native/ and return its body.

    Generic fallback for content not covered by the dedicated tools
    (``get_pattern``, ``get_skill``, ``get_error_doc``, ``load_template``).
    Useful for skill-cross-reference resolution and supplementary files
    (``echolon/native/skills/SKILLS.md``,
    ``echolon/native/errors/codes/README.md``, template READMEs).

    Args:
        path: Relative path under ``echolon/native/`` (e.g.
            ``"skills/SKILLS.md"``, ``"errors/codes/README.md"``,
            ``"templates/minimal/README.md"``). Absolute paths and
            paths escaping the package root are refused with
            ``error="path_outside_native"``.

    Returns ``{path, body}`` on success, or
    ``{error, message, path}`` on failure (path-traversal attempt,
    file not found, not a markdown file).
    

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pathYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior5/5

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

With no annotations provided, the description fully discloses behavior: returns path and body on success, error object on failure with specific error types (path_outside_native). It also explains that absolute paths and escape attempts are refused, providing complete transparency for a read operation.

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?

Description is well-structured with clear sections (Args, Returns) and front-loaded purpose. Though slightly verbose with the docstring format, every sentence adds value and the structure aids readability.

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 a single parameter and simple read operation, the description fully explains purpose, usage context, input format, error handling, and return values. An output schema exists, and the description complements it effectively with behavioral details, leaving no gaps.

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 coverage is 0%, but the description provides detailed semantics for the 'path' parameter: relative path under 'echolon/native/', three concrete examples, and behavior on invalid paths. This adds essential meaning beyond the schema's simple string type.

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 reads any markdown file under 'echolon/native/' and returns its body. It distinguishes itself from sibling tools by naming them as dedicated alternatives (get_pattern, get_skill, get_error_doc, load_template), making purpose unambiguous.

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?

Explicitly identifies as generic fallback for content not covered by dedicated tools, with examples like skill-cross-reference resolution and supplementary files. While it doesn't explicitly say 'do not use when dedicated tools exist', the mention of specific siblings provides clear guidance on when to use alternatives.

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