Skip to main content
Glama

MyAnimeTracker (your list)

My anime list

my_library
Read-onlyIdempotent

List the signed-in person's MyAnimeTracker list: each title with its status (Watching, Completed, Plan to Watch, On Hold, Dropped), score and how many episodes they have watched. Safe-for-work titles only, most recently updated first. For when their shows air next, use whats_airing with mine set to true.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "my_library"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoHow many titles to list, 1 to 50. The most recently updated come first.
statusNoOnly titles with this status. Leave out for all of them.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive/closed-world, so the safety profile is covered. The description still adds real behavior beyond the annotations: results are limited to the signed-in person, adult titles are silently excluded, and ordering is by most recent update.

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?

Two tight sentences: the first front-loads what is returned and its scoping rules, the second handles sibling routing. No filler or redundancy.

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?

For a simple two-optional-param read tool with no output schema, the description supplies the return-field list, ordering, and the SFW restriction, while annotations cover the safety profile. Nothing needed to invoke it correctly is missing.

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?

Schema coverage is 100% and both parameters are well documented in the schema, so the baseline is 3. The prose restates the status vocabulary and the recency ordering but adds no syntax or edge-case meaning beyond the schema.

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?

Names a specific verb and resource ("List the signed-in person's MyAnimeTracker list") and then enumerates the returned fields — status, score, episodes watched — so an agent knows exactly what it gets. The SFW-only and most-recently-updated-first qualifiers sharpen the scope further.

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?

Explicitly routes the agent to a sibling: "For when their shows air next, use whats_airing with mine set to true." That covers the most confusable alternative, but it doesn't say when not to use this tool (e.g. other users' lists, or a title lookup via search_anime).

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources