Skip to main content
Glama

read_article

Read-onlyIdempotent

Fetch the full, untruncated clean Markdown text of a specific engineering article by lang, pillar, and slug. Use this after discovering valid pillar and slug values via search_articles; do not use it for keyword search (use search_articles) or candidate CV details (use get_candidate_profile). Read-only, unauthenticated, no side effects, and subject to a 30 req/min per-IP rate limit. Returns isError: true with invalid_lang, invalid_slug, or article_fetch_404 if the parameters are malformed or the article does not exist.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "lang": "<lang>",
      "pillar": "<pillar>",
      "slug": "<slug>"
    },
    "name": "read_article"
  }
}

Input Schema

NameRequiredDescriptionDefault
langYesRequired article language ("en" for English, "de" for German); must match the article URL.
slugYesLowercase hyphenated article URL slug (without .md).
pillarYesLowercase topic hub slug (e.g., "ai", "security", "architecture", "data", "cloud", "devops", "programming", "career", "lab").

Output Schema

NameRequiredDescriptionDefault
urlYesCanonical HTML article URL.
markdownYesFull untruncated article Markdown.
markdownUrlYesDirect Markdown twin URL.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed6 schema fields changed
    • addedInput schema / properties / lang / description
      Added value: +"Required article language (\"en\" for English, \"de\" for German); must match the article URL."
    • changedInput schema / properties / pillar / description
      Previous value: -"Topic hub slug (e.g. ai, security, architecture, data, cloud)."New value: +"Lowercase topic hub slug (e.g., \"ai\", \"security\", \"architecture\", \"data\", \"cloud\", \"devops\", \"programming\", \"career\", \"lab\")."
    • addedInput schema / properties / pillar / pattern
      Added value: +"^[a-z0-9-]+$"
    • changedInput schema / properties / slug / description
      Previous value: -"Article URL slug."New value: +"Lowercase hyphenated article URL slug (without .md)."
    • addedInput schema / properties / slug / pattern
      Added value: +"^[a-z0-9-]+$"
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "properties": {
      +    "markdown": {
      +      "description": "Full untruncated article Markdown.",
      +      "type": "string"
      +    },
      +    "markdownUrl": {
      +      "description": "Direct Markdown twin URL.",
      +      "type": "string"
      +    },
      +    "url": {
      +      "description": "Canonical HTML article URL.",
      +      "type": "string"
      +    }
      +  },
      +  "required": [
      +    "url",
      +    "markdownUrl",
      +    "markdown"
      +  ],
      +  "type": "object"
      +}
  2. First observed

TDQS

A4.9/5.0
Behavior5/5

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

Beyond the annotations, the description adds the authentication model (unauthenticated), the operational constraint (30 req/min per-IP rate limit), and the failure contract (isError: true with invalid_lang, invalid_slug, or article_fetch_404). These are the details an agent needs to plan calls and handle errors, which annotations alone do not supply.

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?

Three sentences, front-loaded with purpose, then routing guidance, then behavioral constraints. Every sentence carries distinct, load-bearing information with no restatement of the name or schema.

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?

An output schema exists, so return-value documentation is not required, yet the description still covers the error contract. For a three-parameter read tool, all decision-relevant information — purpose, prerequisites, alternatives, rate limit, failure modes — is present.

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

Parameters4/5

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

Schema coverage is 100%, so the baseline is 3, but the description adds value by mapping failure modes to specific parameters (invalid_lang, invalid_slug) and by framing the triple as the article's addressing key. It does not add format or syntax detail beyond the schema, so it stops short of a 5.

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?

States a specific verb and resource — fetching the full, untruncated clean Markdown text of one engineering article — and names the exact addressing triple (lang, pillar, slug). An agent can distinguish it from search_articles or get_candidate_profile without opening any schema.

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

Usage Guidelines5/5

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

Gives explicit sequencing guidance ('use this after discovering valid pillar and slug values via search_articles') and explicit exclusions with named alternatives for keyword search and candidate CV details. Nothing about when to select this tool is left to inference.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources