DXRating

List recent songs

list_recent_songs

Read-onlyIdempotent

Lists the maimai DX songs and charts released recently, by release date, newest first: on each date the new songs, and the new charts added to songs released before, with the level and internal level (譜面定数) of each chart. Use it for "what is new" questions. Release dates are those of Japan.

Input Schema

Name	Required	Description
`days`	No	Release dates from this many days before today (UTC). Default 30.
`limit`	No	Most songs to return, newest dates first, 1 to 200. Default 50.
`since`	No	First release date to list, YYYY-MM-DD. Give since or days, not both.
`server`	No	Game server: jp, intl, usa or cn. Only the charts on that server, with its own level where it differs; a song is new on the date of its first chart there. Omitted: every chart of every server.

Output Schema

Name	Required	Description
`since`	Yes	First release date listed, YYYY-MM-DD
`total`	Yes	Songs released since then, before limit
`server`	Yes	Server of the charts, or null for every server
`source`	Yes
`dataAsOf`	Yes	When the catalog was last updated
`releases`	Yes	Release dates, newest first
`truncated`	Yes	Whether limit left out songs (of the oldest dates)

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedNov 3, 2026

removedOutput schema / properties / source / properties / license

Removed value: -{
-  "const": "CC BY-NC 4.0",
-  "type": "string"
-}

removedOutput schema / properties / source / properties / licenseUrl
```
Removed value: -{
-  "type": "string"
-}
```

changedOutput schema / properties / source / required

Previous value: -[
-  "name",
-  "url",
-  "license",
-  "licenseUrl",
-  "attribution"
-]New value: +[
+  "name",
+  "url",
+  "attribution"
+]

AddedNov 2, 2026

TDQS

A4.1/5.0

Behavior4/5

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

Annotations already establish that this is a safe, read-only, idempotent operation. The description adds meaningful behavioral detail beyond that: ordering is newest first, results are grouped by release date, both new songs and new charts for older songs are included, and dates are Japan-based.

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?

The description is front-loaded with the core behavior and contains no obvious filler. The first sentence is dense but informative, and the later sentences about usage and Japan dates are short and purposeful.

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?

With full schema coverage, rich annotations, and an output schema, the description covers enough for an agent to understand the tool. One minor gap is that 'Release dates are those of Japan' could be read as slightly at odds with the server parameter's server-specific date semantics.

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 description coverage is 100%, so the schema already documents days, limit, since, and server thoroughly. The description adds some date-related context in saying release dates are those of Japan, but it does not materially clarify parameter behavior beyond the schema.

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?

The description states a specific verb and resource: lists recently released maimai DX songs and charts, newest first, including new songs and newly added charts for older songs. It also distinguishes the use case as 'what is new' questions, which separates it from a general song search.

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?

It gives clear usage context: use it for 'what is new' questions. It does not explicitly name alternatives such as search_songs or state when not to use it, so it falls short of full when/when-not guidance.

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

All DXRating tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.