Skip to main content
Glama
Sign In
mcp-mediawiki-crunchtools

mcp-mediawiki-crunchtools

by crunchtools
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Get Category Members Tool

get_category_members_tool
Read-only

Fetch members of a MediaWiki category, including pages, subcategories, or files, and use type filters and pagination to browse large categories.

Instructions

Get pages in a category.

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": {
      "category": "<category>"
    },
    "name": "get_category_members_tool"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMaximum results (default: 50, max: 500)
categoryYesCategory name (with or without "Category:" prefix)
member_typeNoFilter by type: page, subcat, file (default: all)
continue_fromNoContinue token for pagination

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changedv0.2.1
    • addedInput schema / properties / category / description
      Added value: +"Category name (with or without \"Category:\" prefix)"
    • addedInput schema / properties / continue_from / description
      Added value: +"Continue token for pagination"
    • addedInput schema / properties / limit / description
      Added value: +"Maximum results (default: 50, max: 500)"
    • addedInput schema / properties / member_type / description
      Added value: +"Filter by type: page, subcat, file (default: all)"
  2. Changed4 schema fields changedv0.1.4
    • removedInput schema / properties / category / description
      Removed value: -"Category name (with or without \"Category:\" prefix)"
    • removedInput schema / properties / continue_from / description
      Removed value: -"Continue token for pagination"
    • removedInput schema / properties / limit / description
      Removed value: -"Maximum results (default: 50, max: 500)"
    • removedInput schema / properties / member_type / description
      Removed value: -"Filter by type: page, subcat, file (default: all)"
  3. Changed4 schema fields changed
    • addedInput schema / properties / category / description
      Added value: +"Category name (with or without \"Category:\" prefix)"
    • addedInput schema / properties / continue_from / description
      Added value: +"Continue token for pagination"
    • addedInput schema / properties / limit / description
      Added value: +"Maximum results (default: 50, max: 500)"
    • addedInput schema / properties / member_type / description
      Added value: +"Filter by type: page, subcat, file (default: all)"
  4. First observedv0.1.3

TDQS

C2.9/5.0
Behavior2/5

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

The readOnlyHint annotation already establishes this is a safe read. Beyond that, the description adds nothing: it does not mention that results are paginated via a continue token, that limit caps at 500, or that members can be filtered by type. For a tool with 100% annotation coverage of only readOnly, the description should carry more behavioral weight.

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?

A single front-loaded sentence with zero waste. However, the terseness is close to under-specification rather than disciplined conciseness.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

An output schema exists, so return-value explanation is not required, and the input schema is fully described. What is missing is the operational context an agent needs: how category membership relates to subcats/files, and how paging works in practice.

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?

Schema description coverage is 100%, so all four parameters (limit, category, member_type, continue_from) are already fully documented in the schema. The description adds no parameter-level meaning, which is acceptable given the high coverage baseline.

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?

States a clear verb ('Get') and resource ('pages in a category'), which is unambiguous about what the tool returns. It does not distinguish itself from siblings like get_page_categories_tool (the inverse direction) or search_tool, leaving that inference to the agent.

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

Usage Guidelines2/5

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

There is no guidance on when to use this versus list_pages_tool, search_tool, or get_page_categories_tool (which maps page to categories rather than categories to pages). The agent must infer the selection criteria entirely from tool names.

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