Commons Wikimedia

Random Image

random_image

Read-onlyIdempotent

Random image (optionally from a category).

Input Schema

TableJSON Schema

Name	Required	Description	Default
`category`	No

Output Schema

TableJSON Schema

Name	Required	Description	Default
`query`	No
`batchcomplete`	No	Whether the query is complete

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedMay 24, 2026

addedInput schema / examples

Added value: +[
+  {},
+  {
+    "category": "Category:Mountain landscapes"
+  }
+]

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "batchcomplete": {
+      "description": "Whether the query is complete",
+      "type": "boolean"
+    },
+    "query": {
+      "properties": {
+        "categorymembers": {
+          "description": "Category members (when category specified)",
+          "items": {
+            "properties": {
+              "ns": {
+                "description": "Member namespace ID",
+                "type": "number"
+              },
+              "pageid": {
+                "description": "Member page ID",
+                "type": "number"
+              },
+              "title": {
+                "description": "Member title",
+                "type": "string"
+              },
+              "type": {
+                "description": "Type of category member",
+                "enum": [
+                  "page",
+                  "file",
+                  "subcat"
+                ],
+                "type": "string"
+              }
+            },
+            "type": "object"
+          },
+          "type": "array"
+        },
+        "pages": {
+          "items": {
+            "properties": {
+              "imageinfo": {
+                "description": "Image information",
+                "items": {
+                  "properties": {
+                    "height": {
+                      "description": "Image height in pixels",
+                      "type": "number"
+                    },
+                    "mime": {
+                      "description": "File MIME type",
+                      "type": "string"
+                    },
+                    "size": {
+                      "description": "File size in bytes",
+                      "type": "number"
+                    },
+                    "url": {
+                      "description": "File URL",
+                      "type": "string"
+                    },
+                    "width": {
+                      "description": "Image width in pixels",
+                      "type": "number"
+                    }
+                  },
+                  "type": "object"
+                },
+                "type": "array"
+              },
+              "ns": {
+                "description": "Namespace ID",
+                "type": "number"
+              },
+              "pageid": {
+                "description": "Page ID",
+                "type": "number"
+              },
+              "title": {
+                "description": "File title",
+                "type": "string"
+              }
+            },
+            "type": "object"
+          },
+          "type": "array"
+        }
+      },
+      "type": "object"
+    }
+  },
+  "type": "object"
+}

First observedMay 18, 2026

TDQS

B3.1/5.0

Behavior1/5

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

The description claims 'random image' which suggests non-deterministic behavior, but the annotation idempotentHint=true contradicts this by implying the same input yields the same output. This contradiction undermines clarity.

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?

The description is a single sentence that conveys the essential purpose without extraneous words. It is appropriately front-loaded and concise.

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?

Given the tool's simplicity and the presence of annotations and output schema, the description covers basic functionality. However, the contradiction with idempotentHint and lack of details about return format (though output schema exists) leave room for improvement.

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 description adds that the category parameter is optional and filters the image, which is not present in the schema (0% coverage). However, it does not specify valid category formats or provide examples beyond what appears in the schema's examples array.

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 a random image, optionally filtered by category. It distinguishes itself from sibling tools which are unrelated to images.

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?

No guidance on when to use this tool versus alternatives. The description implies its purpose but does not specify any conditions, exclusions, or related tools.

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

All Commons Wikimedia tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.