Skip to main content
Glama

get_sections

Read-onlyIdempotent

Retrieve the list of sections for a Wikipedia article by providing its title.

Instructions

Get the sections of a Wikipedia article.

Returns a dictionary with the article title and list of sections.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
titleYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
titleYes
sectionsYes

Implementation Reference

  • The 'get_sections' tool handler function registered via @register_tool decorator. It takes a 'title' string parameter, calls wikipedia_client.get_sections(title), and returns the result.
    @register_tool("get_sections", model_output_schema(SectionsResponse))
    def get_sections(title: str):
        """
        Get the sections of a Wikipedia article.
    
        Returns a dictionary with the article title and list of sections.
        """
        logger.info("Tool: Getting sections for: %s", title)
        sections = wikipedia_client.get_sections(title)
        return {"title": title, "sections": sections}
  • The WikipediaClient.get_sections() method that fetches the Wikipedia page and extracts its sections using _extract_sections().
    def get_sections(self, title: str) -> List[Dict[str, Any]]:
        """
        Get the sections of a Wikipedia article.
    
        Args:
            title: The title of the Wikipedia article.
    
        Returns:
            A list of sections.
        """
        try:
            page = self.wiki.page(title)
    
            if not page.exists():
                return []
    
            return self._extract_sections(page.sections)
        except Exception as e:
            logger.error(f"Error getting Wikipedia sections: {e}")
            return []
  • The _extract_sections() helper method that recursively extracts section data (title, level, text, subsections) from Wikipedia section objects.
    def _extract_sections(self, sections, level=0) -> List[Dict[str, Any]]:
        """
        Extract sections recursively.
    
        Args:
            sections: The sections to extract.
            level: The current section level.
    
        Returns:
            A list of sections.
        """
        result = []
        for section in sections:
            section_data = {
                "title": section.title,
                "level": level,
                "text": section.text,
                "sections": self._extract_sections(section.sections, level + 1),
            }
            result.append(section_data)
        return result
  • The SectionsResponse model class defining the output schema (title: str, sections: list[dict]) for the get_sections tool.
    class SectionsResponse(MCPBaseModel):
        title: str
        sections: list[dict[str, Any]]
  • The register_tool() decorator that registers the function with FastMCP server under both the original name and 'wikipedia_' prefix, using the output schema.
    def register_tool(name: str, output_schema: dict[str, Any]):
        def decorator(func):
            server.tool(
                func,
                name=name,
                annotations=_READ_ONLY_TOOL_ANNOTATIONS,
                output_schema=output_schema,
            )
            server.tool(
                func,
                name=f"wikipedia_{name}",
                annotations=_READ_ONLY_TOOL_ANNOTATIONS,
                output_schema=output_schema,
            )
            return func
Behavior4/5

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

Annotations already indicate readOnly, idempotent, and openWorld hints. The description adds the return format (dictionary with title and sections), providing useful behavioral context without contradicting 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 two concise sentences, front-loaded with the purpose and followed by the return type. No unnecessary words or details.

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 (one parameter, no nested objects, output schema exists), the description adequately covers purpose, input, and output. Minor improvement could include input format hints, but not essential.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

With 0% schema description coverage, the description adds no extra meaning to the 'title' parameter beyond its name. The parameter is simple and self-explanatory, but the description should compensate for missing schema details.

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 verb 'Get' and the resource 'sections of a Wikipedia article', and specifies the return type as a dictionary with title and list of sections. This distinguishes it from siblings like get_article or get_summary.

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 implicit context for when to use the tool (to retrieve section structure) but lacks explicit guidance on when not to use it or alternatives like get_article for full content.

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/Rudra-ravi/wikipedia-mcp'

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