List Collider RSS section slugs, names, and feed URLs to identify valid categories for collider-headlines requests.
Get Collider RSS sections. Lists the Collider section slugs that collider-headlines accepts, such as movie-news, tv-reviews, trailers, interviews, horror and video-games. Each entry has the slug, display name and feed url. Takes no parameters.
| 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, the description carries the full behavioral burden. It discloses that the tool takes no parameters and describes the return fields (`slug`, `name`, `url`), but it does not mention read-only status, rate limits, caching, or ordering 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?
Three short sentences, front-loaded with the purpose and immediately followed by the sibling relationship, examples, return shape, and parameter note. No wasted text.
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 simple parameterless list endpoint, the description covers what it returns, how it relates to `collider-headlines`, and that no inputs are needed. No output schema exists, so the description responsibly includes the returned fields.
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 and the description says so explicitly. That matches the schema and is sufficient for a parameterless discovery endpoint.
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 verb and resource: it lists Collider section slugs. It explicitly identifies the sibling `collider-headlines` as the consumer and gives concrete slug examples, so an agent can distinguish this tool immediately.
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?
Makes clear that the returned slugs are the accepted inputs for `collider-headlines`, which implies this is a discovery step before calling that sibling. It does not explicitly state when not to use it, but the relationship is clear.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.