MisarBlog MCP Server

Get article

get_article

Read-onlyIdempotent

Fetch a single blog article by its slug and return the full markdown content for reading or processing.

Instructions

Get a single article by slug, including full markdown content

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": {
      "slug": "<slug>"
    },
    "name": "get_article"
  }
}

Input Schema

Name	Required	Description	Default
`slug`	Yes	The article slug

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedv5.2.0Nov 7, 2026
- removedInput schema / additionalProperties
```
Removed value: -false
```

Changed1 schema field changedv5.1.3Oct 14, 2026

changedInput schema / properties / slug / description

Previous value: -"URL slug of the article, e.g. 'how-we-cut-build-times'. Not the numeric id, and not the full URL."New value: +"The article slug"

Changed1 schema field changedv5.1.0Aug 19, 2026

changedInput schema / properties / slug / description

Previous value: -"The article slug"New value: +"URL slug of the article, e.g. 'how-we-cut-build-times'. Not the numeric id, and not the full URL."

First observedv2.0.0Aug 4, 2026

TDQS

A3.6/5.0

Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, so safety is covered. The description does add that the response contains full markdown content, which matters because no output schema exists. It omits what happens on an unknown slug (error vs empty) and any auth/openWorld considerations.

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?

One short sentence, front-loaded with the verb and resource, with the return-content note tacked on where it belongs. Nothing is wasted and nothing needs restructuring.

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?

For a one-parameter read tool with full annotation coverage, the description plus schema is nearly sufficient, and the mention of markdown content compensates for the missing output schema. The main residual gap is not-found behavior.

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% and the single slug parameter is documented in the schema itself. The description only repeats that lookup is by slug and adds no format, casing, or validation details beyond the schema. Baseline 3 is appropriate.

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

Purpose4/5

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

A specific verb (get) plus resource (a single article) with a stated identifier (slug) and payload (full markdown content). It is clearly distinct from list_my_articles and search_articles by the word 'single', though it never names those siblings explicitly.

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

Usage Guidelines3/5

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

Usage is only implied: 'by slug' signals it is for the case where the caller already has a slug, leaving search_articles as the alternative for discovery. There is no explicit when-to-use/when-not-to-use statement or reference to a sibling tool.

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