DXRating

Search songs

search_songs

Read-onlyIdempotent

Finds maimai DX songs by title, alias, nickname, romanization or artist, best match first, with the level and internal level (譜面定数) of each chart. Use it to get the song ID of a song the user names.

Input Schema

Name	Required	Description
`type`	No	Only the songs that have a chart of this type, and only those charts: dx, std, utage or utage2p
`limit`	No	Most songs to return, 1 to 50. Default 10.
`query`	Yes	Title, alias, nickname, romanization or artist, in any language: ウミユリ海底譚, umiyuri, 海底谭, n-buna. Width, case, kana and punctuation are ignored.

Output Schema

Name	Required	Description
`query`	Yes
`songs`	Yes
`total`	Yes	Songs that match, before limit
`source`	Yes
`dataAsOf`	Yes	When the catalog was last updated
`truncated`	Yes	Whether limit left out songs

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"
+]

Changed1 schema field changedNov 2, 2026
- changedOutput schema / properties / songs / items / properties / matched / properties / kind / enum
```
Previous value: -[
-  "title",
-  "acronym",
-  "alias",
-  "artist"
-]New value: +[
+  "title",
+  "alias",
+  "artist"
+]
```
First observedOct 29, 2026

TDQS

A4.1/5.0

Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description adds behavior those annotations cannot convey: results are ranked best-match-first and each chart carries its level and internal level (譜面定数), which tells the agent what to expect from the response.

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 sentences, front-loaded with the match fields and result ordering, ending with the concrete use case. No filler and nothing repeated from the schema verbatim beyond necessary framing.

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?

An output schema exists, so return values need not be fully explained, yet the description still flags the key payload (level and internal level per chart). Combined with 100% schema coverage and clear annotations, an agent has everything needed to call this correctly.

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 query, type and limit are all documented in the schema itself, including normalization rules (width, case, kana and punctuation ignored). The description restates the query field's scope and adds the ranking order but does not extend the type or limit parameters, so baseline 3 applies.

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?

Names a specific verb and resource ('Finds maimai DX songs') and enumerates the matchable fields (title, alias, nickname, romanization, artist) plus result ordering and returned chart data. It does not explicitly distinguish itself from the nearest sibling list_recent_songs, which keeps it from a 5.

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?

'Use it to get the song ID of a song the user names' gives a concrete triggering condition, which is more than implied usage. It stops short of naming alternatives or when-not-to-use cases (e.g., browsing recently played songs vs. searching by name).

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.