Skip to main content
Glama

get_blog_post

Read-onlyIdempotent

Get one blog or engineering post in full by its slug, as markdown, with its author, dates, tags and page.

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_blog_post"
  }
}

Input Schema

NameRequiredDescriptionDefault
slugYesThe post's slug, from search_blog.
sectionNoOptional. "blog" (the default) or "engineering".
languageNoOptional. The language to search and answer in: en, de, fr, es, it, nl, pt, da, sv, nb, fi, pl, ja, cs (a tag like de-DE works too). Defaults to English; a language Bookatu has no catalog for reads English.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare read-only, idempotent, non-destructive, closed-world behavior, so the bar is lower. The description adds genuinely new context by disclosing the return payload (markdown body plus author, dates, tags, page), which the annotations do not cover; it stops short of describing error behavior for unknown slugs.

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?

A single front-loaded sentence that identifies the resource, the key, the format, and the return fields with no redundant wording.

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?

With no output schema, the description usefully enumerates what comes back, which is the main completeness gap for a fetch tool. Only the failure mode (unknown slug, unsupported language fallback) is left unstated, and language fallback is already covered in the schema.

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 description coverage is 100%, so all three parameters, the section enum, and language handling are already documented in the schema. The description's "by its slug" and "blog or engineering" restate schema content rather than adding new meaning, so the baseline of 3 applies.

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?

The description gives a specific verb and resource ("Get one blog or engineering post") plus the access key ("by its slug") and the return form (markdown). It implicitly contrasts with search_blog by stressing a single full post, but does not name or otherwise differentiate against 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 implied: fetch a full post once you have a slug, and the schema note "from search_blog" reinforces the search-then-fetch flow. There is no explicit when-not-to-use guidance or handling for a missing/invalid slug.

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