Skip to main content
Glama

touhou_wiki_get_image_info

Resolve direct image URLs, MIME types, and pixel dimensions for specific MediaWiki File: titles or all images embedded in a Touhou Wiki article.

Instructions

Resolve direct image URLs, MIME types, and pixel dimensions for specific File:... names or all images embedded in a Touhou Wiki article.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "touhou_wiki_get_image_info"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageNoArticle title whose embedded images should be resolved (used if `files` is omitted).
filesNoList of MediaWiki file titles (e.g. ["File:Th20Reimu.png"]).
limitNoMaximum image records to return (1–25, default 10).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.6/5.0
Behavior3/5

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

No annotations exist, so the description carries the full burden. It's evidently a read-only resolution operation, and the description implies the results are informational, but it doesn't state failure behavior (missing files, redirects, non-image files) or whether output is truncated by `limit`. Adequate but thin for a tool with zero annotation coverage.

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?

One sentence, front-loaded with the verb and the concrete return fields, then the two input modes. No filler, no restatement of the tool name.

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?

There's no output schema and no annotations, so the description has to cover behavior and results. It names the return fields, which is helpful, but omits what happens on unknown files or empty results, and doesn't clarify the precedence when both input modes are given.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so the baseline is 3. The description adds real value by stating the either/or relationship between `files` and `page` and by framing what is being resolved, which the schema only partially conveys. It doesn't restate the 1–25 range or default, leaving that to the schema.

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?

The description names a specific verb ('Resolve') and specific outputs (direct image URLs, MIME types, pixel dimensions) over specific inputs (`File:...` names or images embedded in an article). That clearly separates it from siblings like get_page, get_section, and search. It stops short of explicitly naming a sibling tool, so 4 rather than 5.

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?

Usage is implied: pass either file titles or an article page. But it never says when to prefer this over other lookup tools, nor what happens if both `page` and `files` are supplied, nor what happens if neither is supplied (0 required params).

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