Fetch top sports stories from Bleacher Report's public news sitemap, returning current headlines for sports news monitoring.
Get Bleacher Report top stories. Returns fresh Bleacher Report top sports stories from the public news sitemap.
| 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 full burden of behavioral disclosure. It mentions the source ('public news sitemap') and freshness, but does not disclose return format, item count, ordering, or any limits. For a read-only news fetch, this is minimal but not contradictory.
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?
The description is a single, front-loaded sentence that immediately states the verb and resource, and the source detail is appended without excess. Every element earns its place.
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, simple top-stories fetcher, the description states the source and freshness but leaves return structure entirely unstated. With no output schema, an agent cannot know whether the result is a list of objects, how many stories are returned, or what fields are present, which is a notable gap.
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 has zero parameters and the schema is fully covered (100% coverage with an empty properties object). The description does not need to add parameter details, and no parameter semantics are missing.
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 states a specific verb ('Get') and resource ('Bleacher Report top sports stories') and adds a source detail ('public news sitemap'), making the tool's function clear. It does not explicitly differentiate from sibling tools like bleacherreport_headlines, but the phrase 'top stories' provides enough specificity to identify its role.
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 versus siblings such as bleacherreport_headlines, bleacherreport_sections, or bleacherreport_article. No alternatives or exclusions are mentioned, so an agent gets no help choosing between similarly named news tools.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.