Retrieve current MLive top stories, including titles, canonical URLs, summaries, authors, publication times, and images for news monitoring.
Get MLive top stories. Returns current MLive top stories, including title, canonical URL, brief summary, author, publication time, and image where available. Article pages are not currently available, and category endpoints are deferred.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Changes observed during successful MCP inspections.
v1.17.7Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the full burden. It does disclose useful behavior beyond the schema: the exact return fields and the fact that article pages are unavailable and category endpoints are deferred. It omits pagination, freshness/update cadence, and any auth or rate-limit notes, so it adds real but partial value.
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 tight sentences, front-loaded with the purpose before the return details and the availability caveats. Every clause (returned fields, unavailable article pages, deferred categories) carries information an agent can act on.
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 read tool with no output schema, the description supplies the key missing information: the shape of the response and the scope limitations. It is essentially complete for invocation, with only marginal gaps around pagination and update frequency.
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 schema coverage is 100%, so there is nothing for the description to disambiguate. Baseline 4 applies for a parameterless tool.
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 and resource: 'Get MLive top stories', and enumerates the returned fields (title, canonical URL, summary, author, publication time, image). Purpose is unambiguous, though it offers no explicit differentiation from the many sibling *_news/*_headlines tools.
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?
Implied usage as a fetch-top-stories endpoint, with negative guidance that article pages and category endpoints are unavailable. However, it never states when to prefer this tool or names any alternative, leaving selection context to inference.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.