Skip to main content
Glama

get_section

Read-onlyIdempotent

Retrieve a specific section from a PineScript documentation file by its header. Use after listing available sections or identifying the relevant file through search.

Instructions

Get a specific section from a documentation file by its header.

Use after list_sections() shows available headers, or after resolve_topic() / search_docs() identifies the relevant file.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pathYesDocumentation file path (e.g., "reference/functions/strategy.md")
headerYesHeader text to find (e.g., "strategy.exit()" or "## strategy.exit()")
include_childrenNoInclude nested subsections under the header (default: True)

Implementation Reference

  • Registration of the get_section MCP tool via @mcp.tool decorator with tags and annotations.
    @mcp.tool(
        tags={"reference"},
        annotations={"readOnlyHint": True, "idempotentHint": True, "openWorldHint": False}
    )
  • The get_section async handler function that validates the path, reads the doc content, and calls _find_section to extract the section matching the header.
    async def get_section(path: str, header: str, include_children: bool = True):
        """Get a specific section from a documentation file by its header.
    
        Use after list_sections() shows available headers, or after
        resolve_topic() / search_docs() identifies the relevant file.
    
        Args:
            path: Documentation file path (e.g., "reference/functions/strategy.md")
            header: Header text to find (e.g., "strategy.exit()" or "## strategy.exit()")
            include_children: Include nested subsections under the header (default: True)
    
        Returns the section content from the header to the next same-level header.
        """
        with _timed_tool("get_section", path=path, header=header) as log:
            try:
                _validate_path(path)  # check path is allowed
                content = _get_doc_content(path)
                section, start_line, end_line = _find_section(content, header, include_children)
                return f"# {path} (lines {start_line}-{end_line})\n\n{section}"
            except ValueError as e:
                log["error"] = str(e)
                raise ToolError(str(e))
  • _find_section helper: parses markdown headers to locate a section by header text, supporting include_children to stop at same-level or any header.
    def _find_section(content: str, header: str, include_children: bool = True) -> tuple[str, int, int]:
        """Find a section in markdown content by header text.
    
        Returns (section_content, start_line, end_line) or raises ValueError.
        """
        lines = content.splitlines()
    
        # Normalize header query (strip leading #'s if present, collapse whitespace)
        header_text = re.sub(r'\s+', ' ', re.sub(r'^#+\s*', '', header).strip().lower())
    
        start_idx = None
        start_level = None
    
        for i, line in enumerate(lines):
            if line.startswith('#'):
                # Parse header level and text
                match = re.match(r'^(#+)\s*(.+)', line)
                if match:
                    level = len(match.group(1))
                    text = re.sub(r'\s+', ' ', match.group(2).strip().lower())
    
                    if start_idx is None:
                        # Looking for start
                        if header_text in text or text in header_text:
                            start_idx = i
                            start_level = level
                    else:
                        # Looking for end
                        if include_children:
                            # Stop at same level or higher (smaller number)
                            if level <= start_level:
                                return '\n'.join(lines[start_idx:i]), start_idx + 1, i
                        else:
                            # Stop at any header
                            return '\n'.join(lines[start_idx:i]), start_idx + 1, i
    
        if start_idx is not None:
            # Section goes to end of file
            return '\n'.join(lines[start_idx:]), start_idx + 1, len(lines)
    
        raise ValueError(f"Header not found: {header}")
Behavior3/5

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

Annotations already declare readOnlyHint=true and idempotentHint=true. The description does not contradict these and adds no further behavioral context, but consistency is maintained.

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?

Two sentences: first states purpose, second gives usage context. No fluff, perfectly sized.

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?

For a simple retrieval tool with 3 well-documented params and no output schema, the description provides workflow guidance and is complete. Annotations support safety.

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?

Input schema has 100% coverage, so description does not need to add param details. It doesn't add beyond schema, which is adequate meeting baseline.

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 'Get a specific section from a documentation file by its header,' specifying the verb 'Get,' resource 'section,' and qualification 'by its header.' It distinguishes from siblings like get_doc (whole doc) and list_sections (list headers).

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

Usage Guidelines5/5

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

Explicitly states when to use: 'Use after list_sections() shows available headers, or after resolve_topic() / search_docs() identifies the relevant file.' Provides clear context and mentions 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/paulieb89/pinescript-mcp'

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