Skip to main content
Glama

get_todays_birthday_characters

Retrieve a list of characters from AniList whose birthdays are today. Specify the page number to navigate through the results.

Instructions

Get all characters whose birthday is today

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pageNoWhat page in the search to target

Implementation Reference

  • The handler function for the 'get_todays_birthday_characters' tool. It fetches characters with today's birthday using the AniList client, paginated by the input 'page', and returns the JSON stringified data or an error message.
    async ({ page }) => {
      try {
        const characters = await anilist.people.getBirthdayCharacters(page);
        return {
          content: [
            {
              type: "text",
              text: JSON.stringify(characters, null, 2),
            },
          ],
        };
      } catch (error: any) {
        return {
          content: [{ type: "text", text: `Error: ${error.message}` }],
          isError: true,
        };
      }
    },
  • Input schema for the tool, defining an optional 'page' parameter (number, default 1) for pagination.
    {
      page: z
        .number()
        .optional()
        .default(1)
        .describe("What page in the search to target"),
    },
  • Registration of the 'get_todays_birthday_characters' tool using server.tool(), including description, input schema, metadata hints, and inline handler.
    server.tool(
      "get_todays_birthday_characters",
      "Get all characters whose birthday is today",
      {
        page: z
          .number()
          .optional()
          .default(1)
          .describe("What page in the search to target"),
      },
      {
        title: "Get Today's Birthday Characters",
        readOnlyHint: true,
        openWorldHint: true,
      },
      async ({ page }) => {
        try {
          const characters = await anilist.people.getBirthdayCharacters(page);
          return {
            content: [
              {
                type: "text",
                text: JSON.stringify(characters, 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?

With no annotations provided, the description carries full burden but only states the basic function. It doesn't disclose whether this is a read-only operation, how results are returned (e.g., pagination behavior beyond the 'page' parameter), rate limits, authentication requirements, or what happens when no birthdays match today's date.

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 directly states the tool's function with zero wasted words. It's appropriately sized for a simple query tool and front-loads the essential information.

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 simple query tool with one well-documented parameter and no output schema, the description is minimally adequate. However, it lacks important context about return format, pagination behavior, and how 'today' is determined (timezone considerations), which would be helpful given no annotations exist.

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 input schema has 100% description coverage, with the 'page' parameter clearly documented. The description doesn't add any parameter semantics beyond what's in the schema, but since schema coverage is complete, the baseline score of 3 is appropriate.

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' and resource 'characters whose birthday is today', making the purpose immediately understandable. It distinguishes from sibling 'get_todays_birthday_staff' by specifying characters rather than staff, though it doesn't explicitly mention this distinction in the description itself.

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_character' or 'search_character', nor does it mention any prerequisites or contextual constraints. It simply states what the tool does without usage context.

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