Get the list of 7NEWS Australia topic sections accepted by the headlines endpoint, covering national and city news, sport, politics, business, entertainment, lifestyle, and more.
Get 7NEWS Australia sections. Returns the public 7NEWS topic feed inventory accepted by the headlines endpoint: national and city news, sport, politics, business, entertainment, lifestyle and more.
| 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?
No annotations are provided, so the description carries the behavioral burden. It conveys that the endpoint is public and returns an inventory rather than article content, but it does not describe the output shape, value format, or any pagination/limits. Moderate transparency.
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 efficient, front-loaded sentences with no filler. The category examples are compact, and 'and more' avoids an unwieldy exhaustive list.
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 zero-parameter tool with no output schema, the description is mostly sufficient: it names what is returned and how it connects to the headlines endpoint. It could be more precise about the return representation, but the tool's low complexity keeps the gap small.
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 input schema has zero parameters, so the baseline of 4 applies; there is nothing for the description to document. The examples provided are helpful context but are not parameter semantics.
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 the exact verb and resource ('Get 7NEWS Australia sections') and explains that it returns the public topic feed inventory accepted by the headlines endpoint. This clearly distinguishes it from sibling tools like sevennewsau_headlines, sevennewsau_news, sevennewsau_article, and sevennewsau_author.
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 description signals when to use it: when you need the valid 7NEWS section/topic inventory to feed the headlines endpoint. It does not explicitly state when not to use it or name alternatives, but the context is clear enough to guide selection among the sevennewsau_* siblings.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.