Skip to main content
Glama

list_documentation_sections

Read-only

Lists all available documentation sections with descriptions, enabling you to identify and fetch the specific section you need.

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 actual handler function 'list_documentation_sections' that executes the tool logic. It retrieves supported documentation sections from the fetcher, formats them as markdown, and returns the list.
    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 'list_documentation_sections' as a FastMCP tool with annotations including title, readOnlyHint, and description.
    @mcp.tool(
        annotations={
            "title": "List Available Documentation Sections",
            "readOnlyHint": True,
            "description": "Lists all available Ilograph documentation sections with descriptions",
        }
    )
  • The registration call in server.py that invokes register_fetch_documentation_tool(mcp), which registers all documentation tools including list_documentation_sections via the decorator.
    try:
        # Register all tools with error handling
        register_fetch_documentation_tool(mcp)
        logger.info("Registered fetch_documentation_tool")
  • The 'get_supported_documentation_sections()' helper method on IlographContentFetcher that provides the dictionary of section names to descriptions used by the handler.
    def get_supported_documentation_sections(self) -> Dict[str, str]:
        """
        Get the list of supported documentation sections with descriptions.
    
        Returns:
            Dictionary mapping section names to descriptions
        """
        return {
            "resources": "Resource tree organization, hierarchies, instanceOf patterns, abstract resources",
            "relation-perspectives": "Arrow connections, from/to properties, routing, labels, directions",
            "sequence-perspectives": "Time-based diagrams with steps, bidirectional flows, async operations",
            "references": "Resource reference patterns and advanced referencing techniques",
            "advanced-references": "Complex reference scenarios and advanced usage patterns",
            "resource-sizes-and-positions": "Layout control, resource sizing, visual hierarchy management",
            "parent-overrides": "Resource parent overrides in perspectives with scale properties",
            "perspectives-other-properties": "Additional perspective properties and configuration options",
            "icons": "Icon system with iconStyle, icon paths, and categorization",
            "walkthroughs": "Interactive step-by-step guides through diagrams",
            "contexts": "Multiple context views with roots, extends inheritance, context switching",
            "imports": "Namespace management with from/namespace properties, component reuse",
            "markdown": "Rich text support in descriptions, notes, and diagram text",
            "tutorial": "Complete tutorial for learning Ilograph diagram creation",
        }
  • The get_tool_info() helper function that lists 'list_documentation_sections' as one of the registered documentation tools for external reference.
    def get_tool_info() -> dict:
        """Get information about the documentation tools for registration."""
        return {
            "name": "fetch_documentation_tool",
            "description": "Fetches comprehensive Ilograph documentation with markdown formatting",
            "tools": [
                "fetch_documentation_tool",
                "list_documentation_sections",
                "check_documentation_health",
            ],
        }
Behavior4/5

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

Annotations already declare readOnlyHint=true, so the description's addition of returning a formatted list adds value without contradiction.

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 appropriately sized but includes a 'Returns:' line that could be integrated more concisely. Still effective.

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 zero-parameter, read-only list tool with good annotations, the description fully covers what the agent needs to know, including its relationship to fetch_documentation_tool.

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?

There are no parameters, so the description does not need to add parameter information. Baseline score of 4 is appropriate.

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 lists all Ilograph documentation sections with descriptions, using a specific verb and resource. It distinguishes itself from the sibling tool fetch_documentation_tool by focusing on an overview.

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?

The description explicitly says this tool provides an overview and that specific sections can be fetched using fetch_documentation_tool, providing clear when-to-use and when-not-to-use guidance.

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