Skip to main content
Glama

get_recommendation

Retrieve AniList recommendations by ID using the MCP server for accessing AniList API data. Find specific recommendations quickly with this targeted tool.

Instructions

Get an AniList recommendation by its ID

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
recommendIDYesThe AniList recommendation ID

Implementation Reference

  • The async handler function that fetches the AniList recommendation by ID using the anilist client and returns the JSON stringified data or an error message.
    async ({ recommendID }) => {
      try {
        const recommendation = await anilist.recommendation.get(recommendID);
        return {
          content: [
            {
              type: "text",
              text: JSON.stringify(recommendation, null, 2),
            },
          ],
        };
      } catch (error: any) {
        return {
          content: [{ type: "text", text: `Error: ${error.message}` }],
          isError: true,
        };
      }
    },
  • Zod input schema defining the required 'recommendID' number parameter.
    {
      recommendID: z.number().describe("The AniList recommendation ID"),
    },
  • Registers the 'get_recommendation' tool on the MCP server with description, input schema, metadata, and handler.
      "get_recommendation",
      "Get an AniList recommendation by its ID",
      {
        recommendID: z.number().describe("The AniList recommendation ID"),
      },
      {
        title: "Get AniList Recommendation by ID",
        readOnlyHint: true,
        openWorldHint: true,
      },
      async ({ recommendID }) => {
        try {
          const recommendation = await anilist.recommendation.get(recommendID);
          return {
            content: [
              {
                type: "text",
                text: JSON.stringify(recommendation, null, 2),
              },
            ],
          };
        } catch (error: any) {
          return {
            content: [{ type: "text", text: `Error: ${error.message}` }],
            isError: true,
          };
        }
      },
    );
  • tools/index.ts:36-36 (registration)
    Invokes registerRecommendationTools within the registerAllTools function to register all recommendation tools including 'get_recommendation'.
    registerRecommendationTools(server, anilist);
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. It states it 'gets' a recommendation, implying a read-only operation, but doesn't disclose behavioral traits such as authentication needs, rate limits, error handling, or response format. For a tool with no annotations, this leaves significant gaps in understanding its operation.

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 without unnecessary details. It's appropriately sized for a simple lookup tool, with zero waste or redundancy, 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 no annotations, no output schema, and a simple parameter schema, the description is incomplete. It lacks details on behavioral aspects (e.g., what data is returned, error cases) and usage context. For a tool in a server with many siblings, more guidance would help the agent use it correctly in context.

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 description adds minimal meaning beyond the input schema, which has 100% coverage for the single parameter 'recommendID'. It mentions 'by its ID', aligning with the schema's description, but doesn't provide extra context like ID format or examples. With high schema coverage, the baseline score of 3 is appropriate as the schema does the heavy lifting.

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 ('Get') and resource ('AniList recommendation'), specifying it retrieves by ID. It distinguishes from siblings like 'get_recommendations_for_media' by focusing on a single recommendation, though it doesn't explicitly name alternatives. This is specific but lacks direct sibling differentiation.

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?

No guidance is provided on when to use this tool versus alternatives. It doesn't mention prerequisites (e.g., needing a valid recommendation ID), exclusions, or compare with siblings like 'get_recommendations_for_media' for bulk retrieval. The description is minimal, offering no 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