Skip to main content
Glama

jikan_get_character

Read-onlyIdempotent

Retrieve anime or manga character details from MyAnimeList by supplying a character ID. Fetches profile data for a specific character when you have the ID.

Instructions

Get an anime/manga character by MyAnimeList ID.

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": {
      "id": "<id>"
    },
    "name": "jikan_get_character"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesMyAnimeList character ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.1.11

TDQS

B3.2/5.0
Behavior2/5

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

Annotations already declare readOnly, idempotent, openWorld and non-destructive, so the safety profile is covered. The description adds nothing beyond that: no note on invalid-ID behavior, no mention of Jikan's rate limits (a real operational constraint for this API), and no indication of what a successful response contains.

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?

A single front-loaded sentence with no filler or redundancy. It is efficient, though its brevity is partly under-specification rather than deliberate compression.

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?

For a one-param read-only lookup with 100% schema coverage and full annotations, the essentials are present and no output schema is needed. Still missing are the invalid-ID/error case and the API's rate-limit constraint, both of which an agent would benefit from knowing before calling.

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?

Only one parameter and schema description coverage is 100%, so the schema already documents 'id' as the MyAnimeList character ID. The description restates the same fact ('by MyAnimeList ID') without adding format or validation detail, which matches the baseline 3 for a fully documented single param.

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?

States a specific verb (Get) and resource (anime/manga character) plus the lookup key (MyAnimeList ID), which is enough to distinguish it from the jikan_search_* and jikan_get_anime siblings. It stops short of explicitly naming what it is not (there is no character-search sibling, but the get-by-ID vs. search distinction is only implied).

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?

The phrase 'by MyAnimeList ID' implies the precondition that the caller must already hold a numeric MAL character ID, which is a form of usage guidance. There is no explicit when-to-use statement, no mention of what to do without an ID, and no reference to any alternative tool.

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