Skip to main content
Glama
Sign In
wikimedia

wikimedia

by deathrashed
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

wikimedia_get_file

Read-onlyIdempotent

Retrieves metadata for an exact Wikimedia Commons File: title, including original/preview URLs, artist, license, restrictions, upload timestamp, SHA1, and optional preview width.

Instructions

Resolve one exact Commons File: title with original/optional preview URL, artist, license, restrictions, upload timestamp and SHA1. width 0–4096.

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

Input Schema

NameRequiredDescriptionDefault
titleYes
widthNo

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?

Annotations already declare readOnly, idempotent, openWorld and non-destructive, so the safety profile is covered. The description adds the useful return payload and the width bound, but leaves unclear what width=0 produces, whether URLs expire, and what happens for a missing title. Modest added value over the annotations.

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?

Two telegraphic fragments with no filler; the resolution behavior is front-loaded and the width constraint trails as a qualifier. Slightly terse to the point of ambiguity, which costs it the top mark.

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?

With no output schema, the field enumeration does the work of describing the return value, and the rich annotations cover safety. Remaining gaps (error behavior for nonexistent titles, URL lifetime) are minor for a two-parameter read tool.

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%, so the description must carry both parameters. It conveys title must be an exact Commons 'File:' title and hints at width semantics via 'original/optional preview URL' plus 'width 0–4096', but never states that 0 means original and non-zero means a scaled preview, or what the maximum does. Partial compensation only.

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 ('Resolve') and a precise resource ('one exact Commons File: title'), and enumerates the returned fields (URL, artist, license, restrictions, timestamp, SHA1). The word 'exact' plus the enumeration separates it from wikimedia_search_media, though no sibling is named explicitly.

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?

'Resolve one exact Commons File: title' implies the caller must already know the title, which rules out search-style use, but the description never names the alternatives (wikimedia_search_media, wikimedia_download_file, wikimedia_reference_file) or states when to pick this over them.

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