SiteCheck Web Intel

Wikimedia Commons image search: file title, direct image

search_wikimedia_commons_image

Read-only

Wikimedia Commons image search (MediaWiki API, public, no key): file title, direct image URL, size, MIME type, license, author and description for free-licensed files. Returns file metadata only, not image bytes. Usually takes about 14 s, up to 26 s on slower calls; allow a 45 s timeout. Price: $0.002 in USDC per successful call, paid with x402 (Base, Solana or Arc); failed calls are not charged.

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": {
      "q": "<q>"
    },
    "name": "search_wikimedia_commons_image"
  }
}

Input Schema

Name	Required	Description	Default
`q`	Yes	Search words (1 to 200 characters)
`limit`	No	How many images, 1 to 20 (default 5)

Output Schema

Name	Required	Description	Default
`q`	No
`count`	No
`items`	No
`source`	No
`checkedAt`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 23, 2026

TDQS

A4.5/5.0

Behavior5/5

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

Annotations only declare readOnlyHint and openWorldHint; the description adds substantial operational context beyond them: no API key needed, expected latency (~14 s typical, up to 26 s, allow a 45 s timeout), and a cost model of $0.002 USDC per successful call via x402 across Base/Solana/Arc with failed calls uncharged. The latency and pricing disclosures are exactly the kind of facts an agent needs to plan a call, and none of it is inferable from 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.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single dense paragraph that front-loads the identity and payload, then layers on the metadata-only caveat, latency budget, and pricing. Every clause carries distinct information — no restatement of the title and no filler.

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

Completeness5/5

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

With only two simple top-level parameters, an output schema present, and annotations covering the safety profile, the remaining gaps an agent would care about are latency, cost, and auth — all explicitly addressed. Nothing needed to invoke the tool correctly is missing.

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 coverage is 100% and both parameters (q, limit) carry their own descriptions, including the 1–200 character and 1–20 range constraints, so the schema does the semantic work. The description adds no parameter-level detail such as query syntax or how limit interacts with result ordering, making the baseline 3 appropriate.

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?

States a specific verb and resource ("Wikimedia Commons image search") and enumerates the returned fields: file title, direct image URL, size, MIME type, license, author, description. The clause "Returns file metadata only, not image bytes" sharply separates it from any image-download tool, and the source (Wikimedia Commons via MediaWiki API) is unmistakable against the many other search_* siblings.

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

Usage Guidelines4/5

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

The "metadata only, not image bytes" line gives clear situational context for when this tool is the right pick versus fetching an actual image, and the public/no-key note signals no setup is required. It stops short of naming an alternative tool or stating explicit exclusions, so it sits below the top mark.

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

All SiteCheck Web Intel 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.

Resources

Need Help?