Retrieve public Salon RSS section inventory used by the headlines endpoint to identify available sections for headline feeds.
Get Salon RSS sections. Returns the public Salon RSS section inventory used by the headlines endpoint.
| 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 present, so the description carries the behavioral disclosure burden. It conveys that the data is public and the operation is a read-only retrieval, which is useful. However, it does not describe the return shape, possible errors, or any limits, leaving some ambiguity for a no-annotation tool.
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 filler. The action and resource are front-loaded, and the second sentence adds valuable return semantics without redundancy.
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 read-only inventory tool, the description is nearly complete: it names the resource, states it is public, and explains its relationship to the headlines endpoint. It could be slightly stronger by specifying the output format of the section inventory, but nothing essential is missing for invoking 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 input schema has zero parameters, so there are no parameter semantics to document. The description reasonably stays focused on what the tool returns, which is the appropriate baseline for a parameterless tool.
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: 'Get Salon RSS sections.' It also adds a distinguishing purpose by noting this is the 'public Salon RSS section inventory used by the headlines endpoint,' which separates it from sibling tools like salon_news or salon_headlines.
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?
Provides clear context that this tool is meant to supply the section inventory consumed by the headlines endpoint. It does not explicitly list alternatives or exclusions, but the 'used by the headlines endpoint' remark gives an agent a concrete reason to select it.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.