Skip to main content
Glama
Sign In
MyAnimeList MCP Server

MyAnimeList MCP Server

by MorpKnight
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

get_anime_details

Retrieve complete details for any anime using its MyAnimeList ID, with optional selection of specific response fields to tailor the data.

Instructions

Fetch details for one anime, optionally selecting MAL response fields.

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": {
      "anime_id": "<anime_id>"
    },
    "name": "get_anime_details"
  }
}

Input Schema

NameRequiredDescriptionDefault
fieldsNo
anime_idYesMyAnimeList anime ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

C2.7/5.0
Behavior2/5

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

With no annotations provided, the description must carry the full behavioral disclosure. It only indicates a read operation ('Fetch') but does not explain return format, pagination, permissions, rate limits, or side effects. The optional 'fields' hint is the only extra detail.

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 a single, front-loaded sentence with no fluff. It is appropriately short for a simple tool, though the brevity sacrifices useful context.

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?

The tool has no output schema and relies on the description for completeness. However, the description does not explain what 'details' are included, what fields are available, or how it differs from 'get_anime'. This makes it incomplete for an agent deciding whether and how to use it.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The schema provides minimal descriptions for both parameters ('MyAnimeList anime ID' and 'MAL response fields'). The description adds that field selection is optional but fails to explain what valid 'MAL response fields' are, leaving agents to guess. Schema coverage is only 50%, so the description should compensate but does not.

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 clearly states the action ('Fetch') and resource ('details for one anime'), and mentions the optional 'fields' selection. However, it does not distinguish itself from the sibling tool 'get_anime', leaving potential ambiguity about which to use.

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 guidance on when to use this tool versus alternatives like 'get_anime' or 'get_anime_ranking'. It does not describe context, prerequisites, 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