Skip to main content
Glama

get_todays_birthday_staff

Retrieve a list of AniList staff members celebrating their birthday today by querying the AniList MCP server. Specify the search page to organize results efficiently.

Instructions

Get all staff members whose birthday is today

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pageNoWhat page in the search to target

Implementation Reference

  • The handler function that executes the tool's logic: fetches staff members with today's birthday from AniList API using the provided page, stringifies the result as JSON text content, or returns an error.
      async ({ page }) => {
        try {
          const staffMembers = await anilist.people.getBirthdayStaff(page);
          return {
            content: [
              {
                type: "text",
                text: JSON.stringify(staffMembers, null, 2),
              },
            ],
          };
        } catch (error: any) {
          return {
            content: [{ type: "text", text: `Error: ${error.message}` }],
            isError: true,
          };
        }
      },
    );
  • Input schema defining the optional 'page' parameter for pagination in the tool call.
    {
      page: z
        .number()
        .optional()
        .default(1)
        .describe("What page in the search to target"),
    },
  • Registers the get_todays_birthday_staff MCP tool with server.tool(), including name, description, input schema, and metadata (title, hints). The handler is provided as the next argument.
    server.tool(
      "get_todays_birthday_staff",
      "Get all staff members whose birthday is today",
      {
        page: z
          .number()
          .optional()
          .default(1)
          .describe("What page in the search to target"),
      },
      {
        title: "Get Today's Birthday Staff Members",
        readOnlyHint: true,
        openWorldHint: true,
      },
Behavior2/5

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

No annotations are provided, so the description carries full burden for behavioral disclosure. It states the tool retrieves data ('Get all staff members'), implying a read-only operation, but lacks details on permissions, rate limits, pagination behavior (despite a 'page' parameter), or response format. This is inadequate for a tool with no annotation coverage.

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, clear sentence with zero wasted words, efficiently conveying the core purpose. It is appropriately sized and front-loaded, making it easy to parse quickly.

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 the tool's complexity (a filtered query with pagination), lack of annotations, and no output schema, the description is incomplete. It fails to explain behavioral aspects like pagination, return format, or any constraints, leaving significant gaps for an AI agent to understand how to use it effectively.

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 documented as 'What page in the search to target'. The description adds no additional parameter information beyond what the schema provides, so it meets the baseline score of 3 for high schema coverage without compensating value.

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 ('staff members whose birthday is today'), making the purpose specific and understandable. However, it doesn't explicitly differentiate from its sibling 'get_todays_birthday_characters', which serves a similar purpose for a different resource type, missing full sibling distinction.

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, such as 'get_staff' for general staff retrieval or 'get_todays_birthday_characters' for a similar birthday query on characters. There's no mention of prerequisites, exclusions, or contextual usage scenarios.

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