Skip to main content
Glama
gavxm
by gavxm

anilist_taste_card

Read-only

Generate a visual taste profile card for an AniList user, displaying top genres, themes, score distribution, and format breakdown. Get a shareable PNG summary of your anime or manga preferences.

Instructions

Generate a shareable taste profile card image for an AniList user. Returns a PNG image showing top genres, themes, score distribution, and format breakdown. Use when someone wants a visual summary of their anime taste.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
usernameNoAniList username. Falls back to configured default if not provided.
typeNoBuild card from anime or manga listANIME
Behavior4/5

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

Annotations already indicate readOnlyHint=true and destructiveHint=false, so the tool is non-destructive. The description adds value by specifying the output is a PNG image containing specific visual elements (genres, themes, etc.). It does not contradict annotations and provides useful behavioral context.

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 two sentences long, front-loaded with the primary action and output format. Every sentence contributes meaning: first sentence states what it does and output format, second sentence gives use case. No unnecessary words.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool has only two optional parameters, readOnlyHint annotation, and no output schema, the description fully explains what the tool returns (a PNG with taste profile visualizations). It covers the essential behavioral and output details for an agent to invoke correctly.

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 for both parameters ('username' with fallback info, 'type' with anime/manga enum). The description text adds no further parameter-level detail beyond mentioning 'score distribution' which relates to output, not parameters. The baseline of 3 is appropriate as the schema already explains the parameters.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool generates a shareable taste profile card image, specifying it returns a PNG with top genres, themes, score distribution, and format breakdown. This distinguishes it from sibling tools like anilist_compat_card (compatibility card) and anilist_taste (text-based taste info).

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description says 'Use when someone wants a visual summary of their anime taste.' This provides clear context but does not explicitly state when not to use it or list alternative tools. However, given the sibling list, it is adequate for guiding typical use.

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

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/gavxm/ani-mcp'

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