Retrieve Philippine Daily Inquirer top stories from its public RSS feed and return structured JSON for news monitoring and aggregation.
Get Philippine Daily Inquirer top stories. Returns fresh Philippine Daily Inquirer top stories from its public news 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 burden of behavioral disclosure. It adds useful context by noting the source is a 'public news RSS feed' (implying no authentication needed) and that stories are 'fresh'. However, it does not explain pagination, output format, or any other operational details, leaving some gaps for a zero-parameter 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, purposeful sentences. The core action and source are front-loaded, and every word contributes meaning. No redundancy or filler.
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 provides sufficient context: it identifies the publication, the type of content (top stories), and the feed source. It lacks explicit return-format details, but given the simplicity of the operation, this is a minor omission and the description is functionally complete for an agent to invoke it correctly.
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?
There are no parameters, so the input schema is trivially complete. The description adds no parameter semantics because none exist, and none are needed. Per the rubric, 0 params yields a baseline of 4.
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 clearly states the verb 'Get' and the resource 'Philippine Daily Inquirer top stories', explicitly distinguishing it from sibling tools like phillyinquirer_* and other news sources. It also specifies 'from its public news RSS feed', leaving no ambiguity about what this tool returns.
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 no guidance on when to use this tool versus alternatives. While it clearly labels the source as Philippine Daily Inquirer, it does not mention any other news tools or provide conditions for selection, leaving the agent to infer that this is the appropriate tool for this specific publication's headlines.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.