Skip to main content
Glama

list_documentation_sections

Read-only

View available Ilograph documentation sections to understand what content can be fetched for reference and learning.

Instructions

    Lists all available Ilograph documentation sections with descriptions.

    This tool provides an overview of all available documentation sections
    that can be fetched using the fetch_documentation_tool.

    Returns:
        str: Formatted list of available documentation sections with descriptions
    

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The core handler function implementing the logic to list all available Ilograph documentation sections. It retrieves supported sections from the fetcher, formats them into markdown with URLs and usage instructions, and handles errors.
    async def list_documentation_sections(ctx: Context) -> str:
        """
        Lists all available Ilograph documentation sections with descriptions.
    
        This tool provides an overview of all available documentation sections
        that can be fetched using the fetch_documentation_tool.
    
        Returns:
            str: Formatted list of available documentation sections with descriptions
        """
        try:
            await ctx.info("Listing available Ilograph documentation sections")
    
            fetcher = get_fetcher()
            supported_sections = fetcher.get_supported_documentation_sections()
    
            # Format the sections list
            sections_md = "# Available Ilograph Documentation Sections\n\n"
            sections_md += "The following documentation sections are available for fetching:\n\n"
    
            for section, description in sorted(supported_sections.items()):
                url = f"https://www.ilograph.com/docs/editing/{section.replace('-', '/')}/"
                sections_md += f"## {section}\n"
                sections_md += f"**Description:** {description}  \n"
                sections_md += f"**URL:** {url}  \n"
                sections_md += f"**Usage:** Use `fetch_documentation_tool(section='{section}')` to fetch this content\n\n"
    
            sections_md += "---\n\n"
            sections_md += "*To fetch any of these sections, use the `fetch_documentation_tool` with the section name as the parameter.*"
    
            await ctx.info(f"Listed {len(supported_sections)} available documentation sections")
            return sections_md
    
        except Exception as e:
            error_msg = f"Error listing documentation sections: {str(e)}"
            await ctx.error(error_msg)
            return f"Error: {error_msg}"
  • The @mcp.tool decorator that registers the list_documentation_sections tool with FastMCP server, including metadata annotations that define the tool's schema, title, and description.
        annotations={
            "title": "List Available Documentation Sections",
            "readOnlyHint": True,
            "description": "Lists all available Ilograph documentation sections with descriptions",
        }
    )
  • The call to register_fetch_documentation_tool which registers the list_documentation_sections among other documentation tools with the main MCP server instance.
    register_fetch_documentation_tool(mcp)
  • Description of the tool in the server's instructions, providing user-facing schema information.
    - list_documentation_sections: Lists all available documentation sections
Behavior3/5

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

Annotations already declare readOnlyHint=true, indicating this is a safe read operation. The description adds value by specifying that it returns a 'formatted list' and that it provides an 'overview,' which gives context about the output format and scope. However, it doesn't disclose additional behavioral traits like pagination, rate limits, or authentication needs, leaving some gaps despite the annotations.

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 well-structured and concise, using three short sentences that each serve a distinct purpose: stating the tool's function, providing usage context, and describing the return value. There is no redundant or extraneous information, and it is front-loaded with the core purpose.

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?

Given the tool's simplicity (0 parameters, read-only operation), the description is sufficiently complete. It explains what the tool does, hints at its usage relative to another tool, and describes the return format. Since there is no output schema, the description's mention of the return value adds necessary context. Minor gaps include lack of explicit differentiation from siblings and limited behavioral details.

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 0 parameters with 100% coverage, meaning there are no parameters to document. The description appropriately doesn't discuss parameters, focusing instead on the tool's function and output. This meets the baseline for tools with no parameters, as it avoids unnecessary detail while remaining clear about the operation.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool's purpose: 'Lists all available Ilograph documentation sections with descriptions.' It specifies the verb ('Lists'), resource ('Ilograph documentation sections'), and scope ('with descriptions'), making the function unambiguous. However, it doesn't explicitly differentiate from sibling tools like 'list_examples' or 'list_icon_providers_tool' beyond mentioning its specific resource type.

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

Usage Guidelines3/5

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

The description provides some usage context by stating that the listed sections 'can be fetched using the fetch_documentation_tool,' implying this tool is for discovery before fetching. However, it doesn't explicitly state when to use this tool versus alternatives like 'list_examples' or 'check_documentation_health,' nor does it provide exclusions or prerequisites. The guidance is implied but not comprehensive.

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/QuincyMillerDev/ilograph-mcp-server'

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