Skip to main content
Glama
Sign In
wikimedia

wikimedia

by deathrashed
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

wikimedia_list_category

Read-onlyIdempotent

List direct file members of a Wikimedia Commons category without recursing, with paging via a cursor and configurable result limits.

Instructions

List direct file members of a Commons category (not recursive). limit 1–50. Pass continuation.gcmcontinue as cursor for the next page.

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": {
      "title": "<title>"
    },
    "name": "wikimedia_list_category"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
titleYes
widthNo
cursorNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so the safety profile is covered. The description adds real value by disclosing pagination behavior and the cursor mechanic (continuation.gcmcontinue), but says nothing about what a page of results contains or what happens for an empty/nonexistent category.

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?

Three short sentences, front-loaded with the scope constraint, then the limit bound, then the paging instruction. No filler and no repetition of the tool name.

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

Completeness2/5

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

With zero schema description coverage, no output schema, and four parameters, the description should explain the required title format and the width parameter. It covers pagination adequately but leaves an agent guessing about the most important argument and about what the response looks like.

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?

Schema description coverage is 0%, so the description must carry the four parameters, and it does not. It explains cursor (via continuation.gcmcontinue) and restates the limit range already enforced by the schema, but leaves the required `title` ambiguous (with or without a 'Category:' prefix) and never mentions `width` at all.

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 specific verb and resource ("List direct file members of a Commons category") and immediately qualifies scope with "not recursive," so an agent knows it returns direct members only. It does not name any sibling tool, so the differentiation from wikipedia_list_images or wikimedia_search_media is left to inference.

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 parenthetical "(not recursive)" implies when this is the right choice versus a recursive walk, and the cursor sentence describes how to page. There is no explicit statement of when to prefer a sibling like wikimedia_search_media or what prerequisites (category existence, namespace) apply.

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