new_releasesWorks published, or given new episodes, in the last N days (1-30), newest first. section: listen, watch, read or learn (optional).
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"
}
}| Name | Required | Description | Default |
|---|---|---|---|
| days | No | ||
| limit | No | ||
| section | No |
Changes observed during successful MCP inspections.
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint, idempotentHint, non-destructive and openWorld=false, so safety is covered. The description adds ordering (newest first) and the day-window bound, but says nothing about result-set size, the limit parameter, or how 'new episodes' are detected. Adds some context but not rich behavior.
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?
Two short sentences, front-loaded with the core scope, and the optional modifier trailing. No filler, no restatement of the tool name.
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?
For a small read-only browse tool this covers the essentials of scope and ordering, but with 0% schema coverage and no output schema, an agent still lacks information about page size/limit semantics and what a returned 'work' looks like. Adequate, not complete.
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?
Schema description coverage is 0%, so the description must carry the load. It gives meaning to 'days' (recency window) and enumerates the 'section' values, but the 'limit' parameter (default 20, max 60) is entirely undocumented in both schema and description, leaving one of three params opaque.
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?
States a specific resource (works published or given new episodes), a bounded time window (last N days, 1-30) and an ordering (newest first), which is enough to separate it from search/fetch siblings. It stops short of naming an alternative, so it doesn't reach a 5.
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?
The optional section filter hints at usage ('listen, watch, read or learn'), but there is no explicit when-to-use-this vs. search/search_catalogue/list_categories guidance and no indication of what happens when section is omitted. Usage 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.
Add one secure layer between your agents and this server.