Skip to main content
Glama
Sign In
Bangumi MCP

Bangumi MCP

by etherwindy
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

get_character_image

Read-onlyIdempotent

Retrieves a character image URL from Bangumi by specifying character ID and desired size (small, grid, large, medium).

Instructions

获取角色图片 URL

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

Input Schema

NameRequiredDescriptionDefault
character_idYes角色ID
typeYes大小 {small|grid|large|medium}

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.3/5.0
Behavior2/5

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

The description adds no behavioral context beyond the annotations. While annotations already indicate readOnlyHint=true, destructiveHint=false, idempotentHint=true, and openWorldHint=true, the description does not elaborate on what happens if the image does not exist or any other side effects. The minimal description relies entirely on annotations for safety disclosure.

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, concise sentence with no wasted words. It is front-loaded and directly states the tool's purpose.

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 (2 required params, no nested objects, output schema present), the description is minimally adequate. However, it does not provide any additional context about the return format or edge cases, leaving the agent to rely on the schema and annotations alone.

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 100% with both parameters documented (character_id as integer '角色ID', type as string with allowed values). The description does not add any additional parameter semantics, but per guidelines, high coverage yields a baseline score of 3.

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 '获取角色图片 URL' is a specific verb+resource combination that clearly states the tool retrieves a character image URL. It distinguishes itself from sibling tools like get_person_image and get_subject_image by targeting the 'character' entity.

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?

The description provides no usage guidance, such as when to use this tool versus alternatives like get_person_image or get_subject_image. It does not include any context about prerequisites or suitable scenarios.

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