Retrieve your recently played tracks from Deezer. Set the number of results to return with the optional 'first' parameter.
Your recently played tracks.
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_recently_played"
}
}| Name | Required | Description | Default |
|---|---|---|---|
| first | No |
Changes observed during successful MCP inspections.
v1.0.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are present, and the description fails to disclose behavioral traits such as ordering, pagination, or authentication requirements. It does not state that results are for the authenticated user.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is extremely short, which is concise but at the cost of omitting essential information. It could be slightly expanded to include parameter explanation and behavioral details without becoming verbose.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given the lack of output schema and rich annotations, the description is severely incomplete. It does not specify the return format, whether the list is time-ordered, or any additional context the agent needs to correctly invoke the tool.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The only parameter 'first' is not explained in the description. With 0% schema description coverage, the description adds no meaning beyond the schema, leaving the agent to guess its purpose (e.g., limiting the number of tracks).
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description 'Your recently played tracks' clearly indicates the tool retrieves tracks the user has recently played. It effectively distinguishes from sibling tools that deal with albums, artists, playlists, etc. However, it lacks an explicit verb like 'get' or 'list', making it slightly less direct.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
No guidance is provided on when to use this tool versus alternatives such as get_track or get_user_playlists. It does not mention that it returns only tracks and not other content types.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.