mcp-bideetmusique

Read what was just catalogued

list_new_songs

Read-onlyIdempotent

Read recently catalogued Bide & Musique records to see what has just been added, and cap returned feed entries with a limit.

Instructions

Read the records Bide & Musique has just catalogued. The collection is built by hand and grows a few records at a time, so this answers what has been added lately rather than what the station is playing. The feed carries a fixed number of entries and offers no second page, so the count is what it holds and says nothing about how many records the collection has. Entries come in the order the feed publishes them, which runs newest first without being sorted: read 'published_at' rather than the position to date one. Each entry names the song and the artist as one line, which is read apart at the first separator and kept whole under 'listed_as'. Use get_song on the id for the record itself: year, writers, label, duration and the words when the page carries them. When you show a record to a user, credit Bide & Musique and link the page.

Input Schema

Name	Required	Description	Default
`limit`	No	Maximum entries to return, taken from the head of the feed.

Output Schema

Name	Required	Description
`notes`	Yes
`source`	Yes
`results`	Yes
`result_count`	Yes
`entries_in_feed`	Yes	How many entries the feed carries, read or not. It is a fixed window on the newest records, never a count of the collection.

Schema Changelog

Changes observed during successful MCP inspections.

Changed4 schema fields changedv2.1.0Oct 30, 2026
- removedOutput schema / properties / results / items / properties / artist_name / anyOf
```
Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
```
- addedOutput schema / properties / results / items / properties / artist_name / type
```
Added value: +[
+  "string",
+  "null"
+]
```
- removedOutput schema / properties / results / items / properties / published_at / anyOf
```
Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
```
- addedOutput schema / properties / results / items / properties / published_at / type
```
Added value: +[
+  "string",
+  "null"
+]
```
First observedv0.3.0Aug 18, 2026

TDQS

A4.6/5.0

Behavior5/5

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

Goes well past the annotations: fixed feed size with no second page, the count reflects the page not the collection, newest-first ordering that is not sorted so 'published_at' must be read rather than position, the 'listed_as' combined line and how to split it, and a credit/link obligation when presenting records. That is exactly the contextual load the annotations do not carry.

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?

Six sentences, front-loaded with scope before the ordering and format details, and each sentence carries a distinct fact. Some framing ('The collection is built by hand and grows a few records at a time') is atmospheric rather than operational, which costs it the top mark.

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?

With an output schema present, return fields need no explanation, yet the description still supplies ordering semantics, entry shape and the attribution requirement. Nothing an agent needs in order to call this correctly and present results responsibly is missing.

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 100% and already documents limit (default 20, max 50, taken from the head of the feed). The description adds genuinely useful constraint context – the feed has a fixed number of entries and no second page – which explains why the limit behaves as it does, though it never restates the parameter's bounds itself.

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?

Opens with a specific verb and resource ('Read the records Bide & Musique has just catalogued') and immediately scopes it away from what the station is playing. An agent can distinguish this from search_songs or get_random_song without opening any schema.

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?

Explicitly routes the agent onward: 'Use get_song on the id for the record itself' for year, writers, label, duration and lyrics, and contrasts the feed's scope with 'what the station is playing'. It never names search_songs as the alternative for the full collection, so the exclusion is implied rather than stated.

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

Deploy Server