Skip to main content
Glama

New releases / Nowości

new_releases
Read-onlyIdempotent

Newest track pages in the TopAIMuza.pl catalogue of Polish AI music, optionally within one genre: title, artist, release date and links to the track page and the artist profile. Up to 25 tracks. Tracks carry no genre tag of their own: the genre filter uses the artist's genres and leaves out a track whose title names another genre of that artist. / Najnowsze utwory w katalogu TopAIMuza.pl, opcjonalnie w jednym gatunku, z linkami do kart.

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

Input Schema

NameRequiredDescriptionDefault
genreNoGenre slug or Polish name, e.g. disco-polo, rap, pop, rock, dance, biesiada, slaskie. / Gatunek.
limitNoMaximum results to return (1-25, default 10).

Output Schema

NameRequiredDescriptionDefault
okYes
noteNoGuidance for answering, e.g. when nothing was found.
genreNo
queryNo
statusYes
tracksNo
messageNo
returnedNo
total_foundNo
available_genresNo
new_releases_urlNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/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 real behavioral context beyond that: a hard ceiling of 25 tracks, and the non-obvious rule that tracks carry no genre tag, the filter uses the artist's genres, and a track whose title names another of the artist's genres is excluded.

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 English text is front-loaded: purpose first, then the returned fields, then the cap, then the genre-filter caveat. It is somewhat dense, and the Polish half repeats the English rather than adding information, but the content sentences each carry weight.

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 an output schema present, return structure need not be spelled out, and the description still names the key fields. The 25-track cap and genre quirk cover the main surprises for a two-parameter read tool; only explicit ordering guarantees are not stated.

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 the schema already documents both parameters, which sets the baseline at 3. The description adds genuine meaning for genre by explaining it is artist-derived and title-sensitive, but it gives no further signal on how limit interacts with the 25 maximum.

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?

States a specific resource and scope: newest track pages in the TopAIMuza.pl catalogue, with an optional single-genre filter, and lists the fields returned (title, artist, release date, links). The 'newest' framing separates it in spirit from search_tracks or top_ranking, but no sibling is named explicitly.

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?

The optional genre filter is described as the main variation, so a reader can infer 'use this to browse recent additions'. There is no explicit when-not guidance and no pointing to search_tracks (keyword lookup) or top_ranking (popularity ordering) as alternatives.

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