list_recent_newsВръща най-новите новини в хронологичен ред (newest first), with cursor pagination. Use to browse the latest headlines rather than search a specific topic.
| Name | Required | Description | Default |
|---|---|---|---|
| limit | No | How many stories to return (default 15) | |
| cursor | No | ISO timestamp from a previous call's nextCursor, to page to older stories |
Changes observed during successful MCP inspections. Dates show when Glama detected each change.
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the burden for behavioral disclosure. It discloses ordering (newest first), pagination (cursor pagination), and the content type (headlines). It does not explicitly state that it is a read-only operation or describe the return structure, but for a simple list tool, this is reasonably transparent.
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 short and front-loaded, but there is a minor redundancy: 'хронологичен ред' and 'newest first' say the same thing twice. It is still efficient and gets to the point quickly, but has slight waste.
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?
Given the tool's simplicity (read-only list with two optional parameters, no output schema), the description adequately covers the main aspects: what it returns, ordering, pagination, and usage guidance. The absence of an output schema is compensated by the description's mention of 'headlines' and 'news', which sufficiently informs the agent of the expected return content.
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%, with clear descriptions for both limit and cursor. The description adds context that the cursor is used for pagination and that results are chronological, but it doesn't add significant meaning beyond the schema's parameter descriptions. Baseline 3 is appropriate.
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 tool returns the latest news in chronological order (newest first), which is a specific verb+resource+scope. It also differentiates itself from search by saying 'Use to browse the latest headlines rather than search a specific topic', matching sibling search_bulgarian_news.
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 explicitly provides usage guidance: 'Use to browse the latest headlines rather than search a specific topic.' This names the alternative use case (searching a specific topic), which maps to the search_bulgarian_news sibling, and implicitly distinguishes from get_article (getting full article) and get_leading_news (leading/top stories).
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
Each tool has a clearly distinct purpose: search by topic, list chronological, get top-ranked, and fetch details by ID. Descriptions explicitly state when to use each, preventing confusion.
All tools use snake_case with a clear verb (_get_, _list_, _search_) followed by a specific noun, forming a consistent and predictable naming pattern.
4 tools is well-scoped for a news aggregator, covering the core workflows without redundancy or bloat. Each tool earns its place.
The set covers essential news operations (browse, search, top stories, detail view) and supports the main workflow. Minor gaps like category filtering or source-specific queries exist but are not critical.