Retrieve Billboard top stories from public RSS feed. Returns clean JSON for music news and chart updates.
Get Billboard top stories. Returns fresh Billboard top stories from its public RSS feed.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Changes observed during successful MCP inspections.
v1.17.5Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations provided, the description carries the full burden of behavioral disclosure. It does add that the data comes from a public RSS feed and is 'fresh,' which is useful, but it does not disclose any output format, pagination, freshness constraints, or whether it relies on caching. The behavioral information is minimal.
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 with no wasted words. The core action is front-loaded and the RSS source detail is efficiently stated.
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 parameterless news-fetching tool, the description gives the essential source and content type, but with no annotations and no output schema, it leaves out what the returned payload looks like and how it relates to sibling tools like billboard_headlines. It is adequate but not complete for an agent deciding between similar Billboard news tools.
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 tool has zero parameters, so the schema is complete and there is nothing additional that needs explaining. Baseline 4 is appropriate since no parameter semantics are required.
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 clear verb and resource: 'Get Billboard top stories' and notes it returns fresh stories from the public RSS feed. However, it does not distinguish itself from the sibling billboard_headlines tool, which likely serves a similar purpose, so it slightly misses on differentiation.
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 on when to use this tool versus alternatives like billboard_headlines or billboard_sections. The context signals show there are no parameters, but the description does not explain when a user should prefer this over the siblings, nor when not to use it.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.