Skip to main content
Glama
Sign In
wikimedia

wikimedia

by deathrashed
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

wikimedia_download_file

Download an exact Wikimedia Commons file with SHA256 provenance to a configured directory, choosing preview width and max size without overwriting existing files.

Instructions

Download one exact Commons file with provenance JSON/SHA256 beneath the configured download root. Never overwrites. width selects preview; max_mb 1–2048. Requires --download-dir or WIKIMEDIA_DOWNLOAD_DIR.

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_download_file"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNo
titleYes
widthNo
max_mbNo
subdirNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/5.0
Behavior3/5

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

The description adds real behavior beyond the annotations: a provenance JSON/SHA256 sidecar is written, existing files are never overwritten, and a download root must be configured via --download-dir or WIKIMEDIA_DOWNLOAD_DIR. It does not say what happens on a name collision (error vs. skip), and with destructiveHint=false and idempotentHint=false already declared, the remaining gaps are about failure modes rather than the write profile.

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?

Four short sentences, front-loaded with the action and the side-effect contract, then the parameter notes and the prerequisite. Slightly telegraphic, but nothing is wasted.

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 download tool with no output schema, the description covers the destination convention, the sidecar artifact, the no-overwrite guarantee, and the required configuration. An agent could invoke it correctly; only collision behavior and the destination of name/subdir remain unstated.

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 0% across 5 parameters, so the description carries the burden. It clarifies that title must be exact and that width switches to a preview, but "max_mb 1–2048" only restates the schema's min/max, and the name and subdir parameters are never explained.

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?

"Download one exact Commons file" gives a specific verb plus resource and the qualifier "exact" distinguishes it from search-based siblings like wikimedia_search_media. It does not explicitly name wikimedia_get_file or wikimedia_reference_file, so the differentiation with siblings is implied rather than stated.

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 "exact Commons file" phrasing implicitly tells the agent it needs a resolved title (search first), and "width selects preview" signals a preview-versus-original choice. However, there is no explicit when-to-use/when-not guidance and no named alternative for discovering titles or fetching metadata instead of the file.

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