Fetch current headlines from a selected Philippine Daily Inquirer section via its RSS feed. Choose a section slug to receive structured headline data.
Get Philippine Daily Inquirer section headlines. Returns fresh headlines from one Philippine Daily Inquirer section's public RSS feed.
| Name | Required | Description | Default |
|---|---|---|---|
| section | Yes | Philippine Daily Inquirer section slug |
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 burden. It discloses that the feed is public (implying no auth), returns 'fresh' headlines, and is read-only by nature. It does not detail the output format, but for a simple headlines list, this is adequate. No contradictions exist.
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 sentences, zero fluff, with the core action front-loaded. The description is efficient and leaves no redundant content.
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 tool with one enum parameter and no output schema, the description is largely complete: it specifies the source (RSS feed), scope (section), and freshness. It does not specify return field names or count, but the simplicity and clear sibling distinctions make it sufficient.
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 coverage is 100% for the single parameter 'section', which includes an enum and description. The description adds minimal extra meaning—merely reinforcing that headlines come from 'one section'—but does not significantly expand beyond the schema's existing documentation.
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?
The description uses a specific verb ('Get') and resource ('Philippine Daily Inquirer section headlines'), and explicitly ties to a single section's public RSS feed. This clearly distinguishes it from siblings like inquirer_article (full article) and inquirer_news (broader news feed).
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 provides clear context: it fetches headlines for a specific section via RSS feed. It does not explicitly list alternatives or exclusions, but the phrase 'section headlines' implies a focused scope, making it evident when to use this rather than article content tools.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.