Skip to main content
Glama
Sign In
NINJAMCP

NINJAMCP

by omikirin
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python

get_character_image

Retrieve official character illustrations by specifying character name or ID. Optionally select between 2D illustration or 3D model style.

Instructions

キャラクター名またはIDを指定して、そのキャラの公式イラスト画像を返す。styleで2Dイラスト版か3Dモデル版かを選べる。

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": {
      "query": "<query>"
    },
    "name": "get_character_image"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryYesキャラ名またはID。例: '咲耶' 'Shion' '#031'
styleNo画像スタイル。省略時は 2d（イラスト版）

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 are provided, so the description carries the burden. It correctly identifies the tool as a read operation returning images, but does not mention authentication, rate limits, or side effects. Adequate but basic.

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?

Two sentences with no fluff. Purpose is front-loaded, and each sentence adds necessary information.

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

Completeness2/5

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

Lacks specification of the output format (e.g., URL, binary). Without an output schema, the description should clarify what the agent can expect as a return value.

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 the description reiterates parameter details (query as name/ID, style enum). It adds minimal extra value beyond the schema, meeting the baseline.

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 returns official illustrations for a character based on name or ID, with an option to choose 2D or 3D style. It effectively distinguishes from the sibling tool 'search_lore' by focusing on image retrieval.

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?

No explicit guidance on when to use this tool versus the sibling 'search_lore'. The description implies image retrieval vs text lore, but does not state conditions or exclusions.

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