Fetch a public blog article by its slug to read or reference its title, Markdown content, excerpt, cover image, and view count.
Получить статью блога по slug (GET /api/articles/by-slug/{slug}) — публичное чтение, в т.ч. чужие. Возвращает title, content (Markdown), excerpt, coverImage, viewCount.
| Name | Required | Description | Default |
|---|---|---|---|
| slug | Yes | slug статьи (часть адреса /articles/{slug}) |
Changes observed during successful MCP inspections.
v0.11.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description carries the full burden of behavioral disclosure. It states the access scope (public reading), the HTTP method (GET), and the response fields (title, content, excerpt, coverImage, viewCount). It does not mention error handling or rate limits, but the disclosed information is substantial.
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, efficient sentence that packs endpoint, access level, and return structure without redundancy. Every piece of information 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 simple read tool with one parameter and no output schema, the description is complete: it explains what it returns and who can access it. It covers purpose, parameters (via the endpoint), and the result shape, enough for an agent to invoke it correctly.
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 schema already provides 100% coverage for the single parameter, describing slug as the article path part. The description repeats 'by slug' and the endpoint, adding little semantic value beyond what the schema states. 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 specifies the action (get article), resource (blog article), and access method (by slug). It includes the HTTP endpoint and distinguishes from sibling tools like article_list, article_publish, and article_update by focusing on single-article retrieval.
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 implies usage for public reading of any article, including others', but does not explicitly contrast with sibling tools or state when to use this tool instead of listing or publishing. The context is clear but no exclusions or alternatives are named.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.