get_articleВръща пълното резюме на конкретна новина по нейния числов идентификатор (id), заедно с всички източници. Use after search_bulgarian_news or get_leading_news to expand one story by the id shown in its link.
| Name | Required | Description | Default |
|---|---|---|---|
| id | Yes | Numeric article id (from a search/leads result link, e.g. 1234 in /news/1234-...) |
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 full burden. It discloses the key behavior: returns the full summary and all sources. However, it does not mention potential limitations, error cases, or that it is read-only. The description adds some useful context (e.g., id from link) but not comprehensive behavioral disclosure.
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 two sentences: the first states the core purpose in Bulgarian, the second provides usage context in English. It is concise, front-loaded with the function, and contains no redundant 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 simple single-parameter retrieval tool, the description is fairly complete. It states what is returned (full summary and all sources) and provides workflow context with siblings. However, the lack of an output schema and absence of details about response format or pagination mean it is not perfect, but acceptable given the tool's simplicity.
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 input schema already fully describes the id parameter (type, required, exclusiveMinimum, and an example from a link). Since schema coverage is 100%, the baseline is 3. The description reiterates 'id shown in its link' but adds no new semantic information 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?
The description clearly states the tool returns the full summary of a specific news article by numeric id, including all sources. It explicitly distinguishes itself from siblings by indicating it is used after search_bulgarian_news or get_leading_news to expand a single story, which sets it apart from listing and searching 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?
The description provides clear usage guidance: 'Use after search_bulgarian_news or get_leading_news to expand one story by the id shown in its link.' This tells the agent when to invoke the tool, but it does not explicitly mention list_recent_news as an alternative or state when not to use the tool, so it falls short of a perfect 5.
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.