Skip to main content
Glama
JMComic AI

JMComic AI

by hect0x7

get_album_detail

Retrieves detailed information for a specific manga album, including title, author, tags, and stats. Automatically resolves chapter IDs to their parent album details.

Instructions

获取特定本子的详细信息。API 客户端传入子章节 ID 时会自动解析并返回所属父本子的详情。

参数: album_id: 本子 ID (例如 "123456")

返回: 包含详细信息的字典:id, title, author, likes, views, tags, actors, description, chapter_count, update_time, cover_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": {
      "album_id": "<album_id>"
    },
    "name": "get_album_detail"
  }
}

Input Schema

NameRequiredDescriptionDefault
album_idYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/5.0
Behavior3/5

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

With no annotations, the description carries the full burden; it does disclose the important non-obvious behavior that child chapter IDs are auto-resolved to the parent album, and it describes the return payload. It says nothing about authentication requirements (a login sibling exists), error behavior for an invalid ID, or whether missing fields are omitted or null.

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?

Front-loaded one-line purpose followed by clearly labeled parameter and return sections; nothing is padded with marketing language. The enumerated return fields are somewhat redundant given an output schema exists, but they are compact and scannable.

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

Completeness4/5

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

For a single-parameter read tool with an output schema, the description covers the ID semantics, the chapter-to-parent resolution, and the return shape. Gaps are auth preconditions and failure modes, which are secondary but would matter to an agent calling it cold.

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 0%, so the description must compensate, and it does: album_id is documented as a string ID with an example format ("123456") plus the key semantic that a child chapter ID is also accepted and resolved. That is meaningful meaning beyond the bare 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 states a specific verb and resource (get detailed info for a specific album) and adds the non-obvious scope rule that a child chapter ID resolves to its parent album. It does not name a sibling such as search_album or browse_albums to sharpen the boundary, so it stops short of a 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: call this when you already have an album ID (or chapter ID) and want full metadata. The chapter-ID resolution rule is genuinely useful when-to-use context, but there is no explicit guidance on when to prefer search_album/browse_albums instead, and no preconditions such as login requirements.

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