Skip to main content
Glama

List recent or browse alphabetically

list_recent
Read-onlyIdempotent

List recently added anime, manga, people, or companies in the Anime News Network encyclopedia; use starts_with to browse anime and manga titles alphabetically.

Instructions

List what was added to the Anime News Network encyclopedia most recently: anime, manga, people or companies. Pass 'starts_with' to browse titles alphabetically instead, which only applies to anime and manga. Rows carry an id you can pass to get_title when the kind is anime or manga. This walks the catalogue in order: use search_titles when you know the title you are after.

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": "list_recent"
  }
}

Input Schema

NameRequiredDescriptionDefault
kindNoWhich catalogue to list.anime
limitNoHow many rows to return.
offsetNoHow many rows to skip, for paging.
starts_withNoSingle letter. Switches to an alphabetical browse of titles. Anime and manga only.

Output Schema

NameRequiredDescriptionDefault
kindYes
modeYes'recent' is by date added, 'browse' is alphabetical.
rowsYes
notesYes
offsetYes
next_offsetYesPass as 'offset' for the next page. Null when the last page came back short.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed11 schema fields changedv3.0.0
    • addedInput schema / properties / starts_with / minLength
      Added value: +1
    • removedOutput schema / properties / rows / items / properties / date_added / anyOf
      Removed value: -[
      -  {
      -    "type": "string"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]
    • addedOutput schema / properties / rows / items / properties / date_added / type
      Added value: +[
      +  "string",
      +  "null"
      +]
    • removedOutput schema / properties / rows / items / properties / precision / anyOf
      Removed value: -[
      -  {
      -    "type": "string"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]
    • addedOutput schema / properties / rows / items / properties / precision / type
      Added value: +[
      +  "string",
      +  "null"
      +]
    • removedOutput schema / properties / rows / items / properties / source_url / anyOf
      Removed value: -[
      -  {
      -    "type": "string"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]
    • addedOutput schema / properties / rows / items / properties / source_url / type
      Added value: +[
      +  "string",
      +  "null"
      +]
    • removedOutput schema / properties / rows / items / properties / type / anyOf
      Removed value: -[
      -  {
      -    "type": "string"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]
    • addedOutput schema / properties / rows / items / properties / type / type
      Added value: +[
      +  "string",
      +  "null"
      +]
    • removedOutput schema / properties / rows / items / properties / vintage / anyOf
      Removed value: -[
      -  {
      -    "type": "string"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]
    • addedOutput schema / properties / rows / items / properties / vintage / type
      Added value: +[
      +  "string",
      +  "null"
      +]
  2. Changed15 schema fields changedv2.0.0
    • addedInput schema / properties / offset / maximum
      Added value: +9007199254740991
    • changedOutput schema / properties / next_offset / anyOf
      Previous value: -[
      -  {
      -    "type": "integer"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]New value: +[
      +  {
      +    "maximum": 9007199254740991,
      +    "minimum": -9007199254740991,
      +    "type": "integer"
      +  },
      +  {
      +    "type": "null"
      +  }
      +]
    • addedOutput schema / properties / offset / maximum
      Added value: +9007199254740991
    • addedOutput schema / properties / offset / minimum
      Added value: +-9007199254740991
    • addedOutput schema / properties / rows / items / properties / date_added / anyOf
      Added value: +[
      +  {
      +    "type": "string"
      +  },
      +  {
      +    "type": "null"
      +  }
      +]
    • removedOutput schema / properties / rows / items / properties / date_added / type
      Removed value: -[
      -  "string",
      -  "null"
      -]
    • changedOutput schema / properties / rows / items / properties / id / anyOf
      Previous value: -[
      -  {
      -    "type": "integer"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]New value: +[
      +  {
      +    "maximum": 9007199254740991,
      +    "minimum": -9007199254740991,
      +    "type": "integer"
      +  },
      +  {
      +    "type": "null"
      +  }
      +]
    • addedOutput schema / properties / rows / items / properties / precision / anyOf
      Added value: +[
      +  {
      +    "type": "string"
      +  },
      +  {
      +    "type": "null"
      +  }
      +]
    • removedOutput schema / properties / rows / items / properties / precision / type
      Removed value: -[
      -  "string",
      -  "null"
      -]
    • addedOutput schema / properties / rows / items / properties / source_url / anyOf
      Added value: +[
      +  {
      +    "type": "string"
      +  },
      +  {
      +    "type": "null"
      +  }
      +]
    • removedOutput schema / properties / rows / items / properties / source_url / type
      Removed value: -[
      -  "string",
      -  "null"
      -]
    • addedOutput schema / properties / rows / items / properties / type / anyOf
      Added value: +[
      +  {
      +    "type": "string"
      +  },
      +  {
      +    "type": "null"
      +  }
      +]
    • removedOutput schema / properties / rows / items / properties / type / type
      Removed value: -[
      -  "string",
      -  "null"
      -]
    • addedOutput schema / properties / rows / items / properties / vintage / anyOf
      Added value: +[
      +  {
      +    "type": "string"
      +  },
      +  {
      +    "type": "null"
      +  }
      +]
    • removedOutput schema / properties / rows / items / properties / vintage / type
      Removed value: -[
      -  "string",
      -  "null"
      -]
  3. First observedv1.0.0

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/openWorld, so the safety profile is covered. The description adds genuinely non-structured behavior: that 'starts_with' only works for anime and manga, and that returned ids can be chained into get_title. It does not mention rate limits, result caps, or how 'recent' is ordered beyond 'walks the catalogue in order'.

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?

Four tight sentences with the core action front-loaded and the alternative modes following. Slight density in the id/get_title sentence and the trailing search_titles clause, but nothing is wasted.

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

Completeness4/5

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

An output schema exists, so return shape needn't be described, and no parameters are required, keeping the surface simple. The description covers modes, applicability of the browse option, and the handoff to a sibling; only the meaning of 'recent' (ordering or time window) is left implicit.

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%, so all four parameters are already documented, including the starts_with constraint and the limit/offset paging semantics. The description restates the starts_with behavior rather than adding syntax or edge-case detail, so the baseline 3 applies.

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?

States a specific verb and resource ('list what was added to the Anime News Network encyclopedia most recently') and enumerates the four catalogues it covers. It also explicitly separates itself from the alphabetical-browse mode and from the search sibling, so an agent can identify it without opening the schema.

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

Usage Guidelines5/5

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

Gives explicit routing: use this to walk the catalogue in order, pass 'starts_with' to browse alphabetically, and use search_titles when you already know the title. Both the when-to-use and the when-not-to-use alternative are named.

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