Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

Get MyAnimeList character

myanimelist_character_get
Read-onlyIdempotent

Retrieve a MyAnimeList character's profile, attributes, biography, and voice actors by numeric ID to power anime character lookups and enrich app content.

Instructions

Get a MyAnimeList character's profile, attributes, biography and voice actors. Requires 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>",
      "context": "<context>",
      "llm_model": "<llm_model>"
    },
    "name": "myanimelist_character_get"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesRequired. MyAnimeList numeric id.
contextYesDescribe the user's underlying goal in one sentence, not the tool you are calling.
llm_modelYesThe exact model identifier you (the assistant) are running as, taken from your system prompt or environment (for example "claude-opus-4-8" or "gpt-5.2"). Used for analytics only. If you do not know your model identifier with certainty, pass "unknown" and do not guess.
conversation_idNoEcho the conversation_id from the server's previous response. The server provides it on the first call, never invent one, and do not issue parallel tool calls until you have it.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.1

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint, so the safety and idempotency profile is fully covered without the description. The description adds no further behavior beyond content enumeration — no auth requirements, rate limits, or upstream-not-found handling — which is acceptable but not generous given the annotations already carry the load.

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?

Two short sentences, front-loaded with the resource description. The trailing 'Requires `id`' is redundant with the schema's required array and its own parameter description, costing a small amount of precision but not clarity.

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 simple read-only lookup with full annotation coverage and complete schema descriptions, the description is sufficient: it names the resource and the returned fields, and the schema handles the analytics parameters and conversation_id. The main omission is any routing hint toward the list-based sibling endpoints.

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%, including the note that `id` is a required MyAnimeList numeric id, so the baseline is 3. The description's 'Requires `id`' merely restates the schema and adds no format or constraint detail beyond it.

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 gives a specific verb ('Get') and resource ('MyAnimeList character') and enumerates the returned content (profile, attributes, biography, voice actors), so the agent knows exactly what the tool retrieves. It does not, however, contrast itself with the closest sibling, myanimelist_anime_characters_list, which returns characters for a title rather than one character by id.

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 only usage signal is 'Requires `id`', which is a prerequisite rather than guidance. There is no statement of when to prefer this single-character lookup over the sibling list endpoint, and no mention of failure behavior for unknown ids.

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