Skip to main content
Glama

get_character

Retrieve detailed information about a specific character using their AniList ID or name, accessible via the AniList MCP server.

Instructions

Get information about a character by their AniList ID or name

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesThe AniList ID of the character

Implementation Reference

  • The handler function for the 'get_character' tool. It takes an ID or name, fetches the character data from AniList, and returns it as a formatted JSON string, with error handling.
      async ({ id }) => {
        try {
          const character = await anilist.people.character(id);
          return {
            content: [
              {
                type: "text",
                text: JSON.stringify(character, null, 2),
              },
            ],
          };
        } catch (error: any) {
          return {
            content: [{ type: "text", text: `Error: ${error.message}` }],
            isError: true,
          };
        }
      },
    );
  • Input schema for the 'get_character' tool using Zod, accepting either a numeric ID or string name for the character.
    {
      id: z
        .union([z.number(), z.string()])
        .describe("The AniList ID of the character"),
    },
  • tools/people.ts:14-44 (registration)
    Registration of the 'get_character' MCP tool within the registerPeopleTools function, including name, description, input schema, hints, and handler.
      "get_character",
      "Get information about a character by their AniList ID or name",
      {
        id: z
          .union([z.number(), z.string()])
          .describe("The AniList ID of the character"),
      },
      {
        title: "Get Character Info",
        readOnlyHint: true,
        openWorldHint: true,
      },
      async ({ id }) => {
        try {
          const character = await anilist.people.character(id);
          return {
            content: [
              {
                type: "text",
                text: JSON.stringify(character, null, 2),
              },
            ],
          };
        } catch (error: any) {
          return {
            content: [{ type: "text", text: `Error: ${error.message}` }],
            isError: true,
          };
        }
      },
    );
Behavior2/5

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

No annotations are provided, so the description carries the full burden. It states it's a read operation ('Get information'), implying no destructive effects, but lacks details on permissions, rate limits, error handling, or response format. For a tool with zero annotation coverage, this is a significant gap in behavioral disclosure.

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

Conciseness5/5

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

The description is a single, efficient sentence that front-loads the core purpose ('Get information about a character') and specifies input methods. There is no wasted wording, making it highly concise and well-structured for quick understanding.

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?

Given no annotations and no output schema, the description is incomplete. It doesn't explain what information is returned (e.g., character details, media appearances), error cases, or behavioral traits like authentication needs. For a tool with rich sibling context and no structured support, more completeness is needed.

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?

The schema description coverage is 100%, with the parameter 'id' documented as accepting 'AniList ID of the character' with type number or string. The description adds that it can also use 'name', which isn't reflected in the schema, providing some extra semantic value beyond the structured data.

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 verb ('Get information') and resource ('about a character'), specifying it can be done by 'AniList ID or name'. However, it doesn't explicitly differentiate from sibling tools like 'search_character' or 'get_todays_birthday_characters', which would require more specific scope or context.

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 'search_character' or 'get_todays_birthday_characters'. It mentions the input methods (ID or name) but doesn't clarify scenarios, prerequisites, or exclusions for tool selection.

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

Install Server

Other Tools

Related Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/yuna0x0/anilist-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server