Fetch PC Gamer top stories with titles, URLs, and optional summaries, authors, publication times, and images.
Get PC Gamer top stories. Returns the current PC Gamer top stories, with no parameters. Each item has a title and URL, and may include summary, author, publication time and image. Use pcgamer-headlines to read one section.
| 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 must carry behavioral weight, and it does disclose the return shape: each item has title and URL plus optional summary, author, publication time and image. It omits freshness/quantity/pagination behavior ("current" is the only hint), which keeps it short of a 5.
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?
Three tight sentences with purpose front-loaded, then return contents, then sibling routing. Every sentence earns its place; nothing is padded.
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?
With no output schema and no parameters, the description usefully explains what comes back and how it relates to the headlines tool. It could say more (number of stories, ordering, freshness) but is adequate for a straightforward read-only feed.
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 tool takes zero parameters, and the description confirms "with no parameters," matching the empty schema. Per the rubric, a 0-param tool has 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?
States a specific verb+resource ("Get PC Gamer top stories") and names a sibling (pcgamer-headlines) that it is not, distinguishing the two scopes. The hyphen/underscore naming mismatch with the actual sibling list is a minor wrinkle, and it only differentiates against one of the four pcgamer siblings.
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?
Explicitly routes the agent: "Use pcgamer-headlines to read one section," giving an alternative and the condition that selects it. It stops short of stating when NOT to use this tool (e.g., for a single article or author feed), so it is clear context without exclusions.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.