Bangumi MCP

get_index_subjects

Read-onlyIdempotent

Retrieve entries from a Bangumi directory. Filter by subject type and control pagination with limit and offset.

Instructions

获取目录中的条目列表

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": {
      "index_id": "<index_id>"
    },
    "name": "get_index_subjects"
  }
}

Input Schema

Name	Required	Description	Default
`index_id`	Yes	目录ID
`params`	No	可选参数，包含条目类型、分页限制和偏移量

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Jun 18, 2026

TDQS

B3.4/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, idempotentHint=true. The description does not contradict these and adds no additional behavioral context such as pagination behavior, error handling, or rate limits. It meets the minimum bar but does not enrich the agent's understanding.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

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

The description is very concise: a single sentence. It is front-loaded with the key purpose. However, it could be slightly expanded to include behavioral notes without losing conciseness. It earns its place but is minimal.

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 has nested parameters and an output schema, the description is quite sparse. It does not explain that the `type` parameter filters by subject category or that pagination is via limit/offset. However, with full schema coverage and output schema present, the description is minimally adequate but not complete.

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%, so parameters are fully documented in the schema. The description adds no additional meaning beyond the schema. Baseline score of 3 is 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?

The description clearly states the verb (获取/get) and resource (目录中的条目列表/list of entries in a directory). It is specific and distinguishes from sibling tools like get_index_info (which gets index metadata) and delete_index_subject (which deletes). The purpose is unambiguous.

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 is provided on when to use this tool versus alternatives. For example, it does not explain when to prefer get_index_subjects over get_index_info or get_subjects. The description lacks context on prerequisites or typical usage scenarios.

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

Deploy Server