Skip to main content
Glama

What is airing

whats_airing
Read-onlyIdempotent

List anime episodes airing over the next few days, by Japan broadcast date, from the MyAnimeTracker calendar, with broadcast times. Set mine to true for when the person's own shows air next. Safe-for-work titles only. Episode numbers and dates only.

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

Input Schema

NameRequiredDescriptionDefault
daysNoHow many days ahead to list, starting today in Japan. 1 to 14.
mineNoOnly the shows on the signed-in person's list: Watching and Plan to Watch, on any season of the series. Needs sign-in.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / mine
      Added value: +{
      +  "default": false,
      +  "description": "Only the shows on the signed-in person's list: Watching and Plan to Watch, on any season of the series. Needs sign-in.",
      +  "type": "boolean"
      +}
  2. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already cover safety (readOnly, idempotent, non-destructive, closed-world), so the description earns credit for what it adds: a content filter ('Safe-for-work titles only'), a payload limitation ('Episode numbers and dates only'), a timezone/ordering rule, and the data source. The sign-in requirement for 'mine' is stated, though it is also duplicated in the schema.

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 short sentences, front-loaded with scope and timezone before the mode flag and the content caveat; nothing is redundant with itself. The clipped fragments ('Safe-for-work titles only. Episode numbers and dates only.') are efficient but slightly telegraphic, keeping it off a 5.

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?

For a two-optional-parameter read tool with no output schema, the description covers scope, time window, timezone, filtering, mode switching, and roughly what comes back. The only real gap is the shape/ordering of the returned list, which 'Episode numbers and dates only' gestures at but does not fully specify.

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% — both 'days' (1-14, Japan-based) and 'mine' (Watching/Plan to Watch, needs sign-in) are fully documented in the schema. The description echoes the 'mine' behavior but adds no format, boundary, or edge-case detail beyond what the schema already provides, so 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 anime episodes airing') plus the time window ('over the next few days'), the ordering basis ('by Japan broadcast date'), and the data source ('MyAnimeTracker calendar'). None of the siblings (get_filler_guide, get_watch_order, popular_anime, search_anime) is a schedule tool, so the distinction is unambiguous without needing an explicit exclusion.

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?

'Set mine to true for when the person's own shows air next' gives a concrete conditional for switching modes, and the SFW constraint tells the agent when this is the appropriate tool. It stops short of naming when NOT to use it or pointing at a sibling for adjacent needs (e.g. a full series list), so it is clear context rather than full routing guidance.

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