Skip to main content
Glama

animechan_search

Read-onlyIdempotent

Search for anime quotes by specific anime title to retrieve memorable lines from a chosen series.

Instructions

Search for anime quotes from a specific anime.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "anime": "<anime>"
    },
    "name": "animechan_search"
  }
}

Input Schema

NameRequiredDescriptionDefault
animeYesAnime title to search quotes from

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.1.11

TDQS

C2.9/5.0
Behavior2/5

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

Annotations already declare readOnly, idempotent, openWorld, and non-destructive, so the safety profile is covered. The description adds nothing beyond that: it doesn't say whether the title match is exact or fuzzy, how many quotes come back, or what happens on a miss for a tool whose whole value hinges on matching behavior.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single front-loaded sentence with no filler or redundancy. It is efficiently structured, though the brevity comes at the cost of substance rather than being a model of tight completeness.

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?

No output schema exists, so the description carries the burden of explaining what comes back (quote text, character name, anime title, count), and it says nothing. For a simple lookup this is a noticeable gap that forces the agent to call blind.

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?

With one parameter at 100% schema coverage, the schema already documents 'anime' as the title to search, so the baseline of 3 applies. The description could have clarified matching semantics (partial title, case sensitivity, aliases) but simply restates the parameter.

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 names a specific verb and resource ('Search for anime quotes') and scopes it to a specific anime, which is clear. It doesn't differentiate it from the sibling animechan_random (fetch quotes from anywhere) or from jikan_search_anime, so the agent must infer which tool to use.

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?

There is no statement of when to use this versus animechan_random or the jikan anime search siblings, and no guidance on what happens if the title is wrong or unknown. The only implied usage comes from the required parameter, which the schema already conveys.

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

Deploy Server

Other Tools