Fetch current GMA News headlines from any chosen section RSS feed, returning clean structured headline data for news monitoring and aggregation.
Get GMA News section headlines. Returns fresh GMA News Online headlines from one public section RSS feed.
| Name | Required | Description | Default |
|---|---|---|---|
| section | Yes | GMA News 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, the description carries the burden and does communicate that this reads a public RSS feed and returns fresh headlines, implying a read-only public operation. However, it does not disclose output shape, rate limits, or behavior around unavailable/empty sections, which would be needed for full 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 short sentences, no filler, and the core purpose is front-loaded. Every element (GMA News, section, headlines, RSS feed) adds useful information.
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 one-required-parameter public headlines tool, the description plus enum schema is enough to select and invoke it correctly. There is no output schema and the description does not detail the returned headline structure, but 'returns fresh... headlines' is adequate given the simple resource.
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 description coverage is 100% and the single 'section' parameter is described as 'GMA News section slug' with an enum. The description adds that headlines come from a section RSS feed, but adds no new meaning about the parameter's values or format beyond the schema.
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?
Description uses a specific verb ('Get'), resource ('GMA News section headlines'), and source scope ('one public section RSS feed'), so an agent can tell it is the headlines-for-a-section tool rather than gmanews_sections or gmanews_news. It does not explicitly name or contrast those siblings, so it falls just short of a 5.
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?
There is no guidance on when to use this tool instead of sibling tools like gmanews_sections or gmanews_news, and no exclusion criteria or alternatives are mentioned. The intended use is implied by the name and description only.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.