Skip to main content
Glama
smeet666

mcp-animenewsnetwork

by smeet666
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Read the news wire

get_news
Read-onlyIdempotent

Retrieve current Anime News Network stories from RSS feeds. Filter by category, feed type, or edition to get relevant anime news, reviews, and features.

Instructions

Read the latest Anime News Network stories from their RSS feeds. 'all' mixes news, reviews and features; 'news' and 'reviews' are the narrower feeds. Filter with 'category' to keep only stories the feed tags a given way, such as Manga or Anime. The feed is the whole window available: there is no way to reach older stories through this tool. When you repeat a story, cite Anime News Network and link the article.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
feedNoWhich feed to read. 'all' is the busiest.all
limitNoHow many stories to return.
editionNoRegional edition. They differ mostly in release and licensing coverage.us
categoryNoKeep only items tagged this way, matched case-insensitively.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
feedYes
itemsYes
notesYes
editionYes
total_availableYesItems in the feed after 'category' was applied, before 'limit'.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed8 schema fields changedv2.0.0
    • addedOutput schema / properties / items / items / properties / category / anyOf
      Added value: +[
+  {
+    "type": "string"
+  },
+  {
+    "type": "null"
+  }
+]
    • removedOutput schema / properties / items / items / properties / category / type
      Removed value: -[
-  "string",
-  "null"
-]
    • addedOutput schema / properties / items / items / properties / published_at / anyOf
      Added value: +[
+  {
+    "type": "string"
+  },
+  {
+    "type": "null"
+  }
+]
    • removedOutput schema / properties / items / items / properties / published_at / type
      Removed value: -[
-  "string",
-  "null"
-]
    • addedOutput schema / properties / items / items / properties / summary / anyOf
      Added value: +[
+  {
+    "type": "string"
+  },
+  {
+    "type": "null"
+  }
+]
    • removedOutput schema / properties / items / items / properties / summary / type
      Removed value: -[
-  "string",
-  "null"
-]
    • addedOutput schema / properties / total_available / maximum
      Added value: +9007199254740991
    • addedOutput schema / properties / total_available / minimum
      Added value: +-9007199254740991
  2. First observedv1.0.0

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already establish the operation is read-only, idempotent, non-destructive, and open-world. The description adds useful behavior beyond that: the feed is the entire available window, category matching is case-insensitive, and stories repeated by the agent must cite and link Anime News Network.

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?

Four compact sentences, each earning its place: purpose, feed semantics, retrieval-window limitation, and citation obligation. The most important operational constraints are front-loaded before the optional citation note.

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?

With an output schema, annotations, and 100% schema parameter coverage, the description fills the remaining gaps: feed-scope meaning, unavailability of older stories, category filtering semantics, and attribution behavior. Nothing needed to call the tool correctly is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema descriptions already cover all four parameters, so the baseline is 3. The description adds value by explaining what 'all' means relative to 'news' and 'reviews', and by giving concrete category examples plus case-insensitive matching, which goes beyond the schema.

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 tool reads the latest Anime News Network stories from RSS feeds and explains the feed variants. It does not explicitly name sibling tools or say how it differs from search_titles, get_title, or list_recent, so it is clear but lacks explicit 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 Guidelines4/5

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

The description gives clear context: it covers only the current RSS window and states there is no way to reach older stories, which implies historical retrieval is not this tool's job. However, it never names an alternative tool for older or search-based lookups, so it stops short of explicit when-to-use versus alternatives.

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