Skip to main content
Glama

get_article

Read-onlyIdempotent

Fetch the Markdown body and metadata of a blog article using its slug. Returns article details or an error if the slug is invalid.

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
Behavior5/5

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

Annotations already declare readOnlyHint and idempotentHint true. The description adds the error behavior (returns article with error field on missing slug) and the return content structure (Markdown body plus metadata). This provides additional useful behavioral context beyond the annotations.

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?

The description is concise: two sentences. The first states the primary purpose, the second covers return type and error case. No redundant or extra information. Every word contributes.

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

Completeness4/5

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

Given the simple nature of the tool (one parameter, no nested objects, output schema exists), the description adequately covers retrieval and error handling. Missing discussion of authentication or rate limits, but these are not critical for this read-only, idempotent tool. Overall complete enough.

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 detailed parameter description. The tool description does not add new information about the slug parameter beyond what the schema already provides. Baseline score of 3 is appropriate for this case.

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 verb 'retrieve', the resource 'blog article', and the key parameter 'slug'. It distinguishes from sibling tools like 'search_blog' by focusing on full content retrieval. The purpose is specific and unambiguous.

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 indicates when to use the tool (to get full article content by slug). It implicitly guides usage after search_blog via the parameter description. However, it lacks explicit when-not or alternative tool references, which would elevate it to 5.

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