Skip to main content
Glama

get_article

Read-onlyIdempotent

Retrieve the full Markdown content and metadata of a blog article by providing its slug. If the slug does not match any article, an error is returned.

Instructions

Retrieve the full content of a blog article by its slug.

Returns the article body (Markdown) plus metadata. If the slug does not match any article, returns an Article with error='article_not_found' and other fields at their defaults.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
slugYesArticle slug as returned by search_blog (e.g. 'setup-mistral-sglang-setup'). Lower-case, hyphenated.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
slugYesArticle slug
titleNoArticle title
urlNoPublic URL of the article
dateNoPublication date (ISO 8601)
tagsNoTopic tags assigned to the article
descriptionNoShort article description
bodyNoFull article body in Markdown
quality_scoreNoBuild-time quality score from the editorial pipeline (unbounded weighted composite across 13 signals, higher is better; thresholds depend on style)
quality_styleNoEditorial style category (e.g. 'best_practice_learnings', 'werthaltige_code_beispiele'). Empty if not categorised.
quality_classNoEditorial content class (e.g. 'Ephemeral', 'Evergreen'). Empty if not classified.
word_countNoWord count of the article body
errorNoSet to 'article_not_found' if no article matches the slug
Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already provide readOnlyHint and idempotentHint. The description adds value by specifying return content (Markdown body + metadata) and the explicit error field when slug is not found, which is beyond annotation information.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two concise sentences, front-loaded with purpose, then return/error details. Every sentence adds value with no redundancy.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the simplicity of the tool (one parameter) and existing annotations/output schema, the description sufficiently covers purpose, input, return, and error handling.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% with a good description of the slug parameter (example, format). The description adds little beyond restating 'by its slug', so baseline 3 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the action ('Retrieve the full content') and the resource ('a blog article by its slug'). It is distinct from sibling tools like search_blog or list_tags, as it targets a single article via a unique slug.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies that the slug comes from search_blog (via example in schema) and explains the error behavior for non-matching slugs. However, it does not explicitly state when to prefer this tool over siblings, though the context is clear.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/cipherfoxie/sovereign-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server