Skip to main content
Glama
Sign In
Grokipedia MCP Server

Grokipedia MCP Server

by fastmcp-me
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

get_page_sections

Read-onlyIdempotent

Lists all section headers of a Grokipedia article using its unique slug for quick content navigation.

Instructions

Get a list of all section headers in an article.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "slug": "<slug>"
    },
    "name": "get_page_sections"
  }
}

Input Schema

NameRequiredDescriptionDefault
slugYesUnique slug identifier of page to list sections for

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.2

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and idempotentHint=true, so the safe, non-destructive behavior is clear. The description adds the output context ('section headers') but no additional behavioral details (e.g., ordering, pagination). Given strong annotations, this is adequate.

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?

A single, front-loaded sentence that efficiently conveys the tool's purpose without redundancy. Every word adds value.

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?

For a simple list tool with one required parameter and strong annotations, the description is sufficient to convey what the tool does and returns. It doesn't document edge cases or output format, but the tool's simplicity reduces the need for more.

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?

The schema provides full description for the single 'slug' parameter (100% coverage). The description adds that the tool lists 'all section headers', implying the output but not adding extra parameter semantics. Baseline is met.

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 retrieves 'all section headers in an article', with a specific verb ('Get'), resource ('section headers'), and context ('in an article'). It distinguishes from sibling tools like 'get_page_section' (singular) and 'get_page_content'.

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 implies usage for listing section headers but provides no explicit guidance on when to use this tool versus alternatives like 'get_page_section' or 'get_page_content'. No when-not-to-use or pre-conditions are stated.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools