mcp-aoty

get_new_releases

Browse recently released albums from Album of the Year's release feed. Specify a page number to view older releases.

Instructions

List recently released albums, ordered by AOTY's release feed.

Args: page: One-based page number for older releases.

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

Input Schema

Name	Required	Description	Default
`page`	No

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Sep 1, 2026

TDQS

A4.2/5.0

Behavior4/5

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

With no annotations, the description carries the disclosure burden. It covers ordering ('ordered by AOTY's release feed') and pagination semantics ('page: One-based page number for older releases'), giving useful behavioral context beyond the bare purpose.

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 short, front-loaded sections with no filler. The purpose is stated first, followed by a compact parameter note. Every sentence adds information.

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?

Given the low complexity, one optional parameter, and presence of an output schema, the description is largely complete. It covers what is returned, the ordering, and pagination, though the 'recently released' window itself is not precisely defined.

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 coverage is 0%, but the description compensates for the only parameter by explaining that page is one-based and is used to fetch older releases. This adds meaning beyond the plain schema property.

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 recently released albums'. It also names the ordering source, 'AOTY's release feed', which distinguishes it from sibling tools like get_new_singles and get_upcoming_releases.

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

Usage Guidelines3/5

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

Usage is implied by 'recently released albums' and the page argument for 'older releases', but there is no explicit guidance about when to prefer this tool over siblings like get_new_singles or get_upcoming_releases, nor any exclusions.

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

Deploy Server