Skip to main content
Glama

Read a blog article

get_post
Read-only

One blog article as markdown, with its title, date, tags and URL. Get the slug from search.

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

Input Schema

NameRequiredDescriptionDefault
slugYesThe article slug, the last part of its URL.
localeNoLanguage of the content: en or fr.en

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description usefully adds that output is markdown plus metadata fields, but says nothing about failure behavior for a missing slug or how the default locale 'en' behaves when a translation is absent.

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 short sentences with zero padding; the return shape is front-loaded and the slug-prerequisite hint follows immediately.

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 simple two-parameter read tool with full schema coverage and annotations carrying the safety profile, the description covers what it returns and how to obtain the required input. Only error/not-found behavior is left implicit, a minor gap given the tool's simplicity.

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 both parameters are documented in the schema, including the locale enum and default, so the baseline is 3. The description adds only the provenance of the slug ('from search'), which is genuinely helpful but does not explain locale semantics or fallback.

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?

Identifies the specific resource (a single blog article) and its return shape (markdown plus title, date, tags, URL), which clearly separates it from sibling tools like get_app, get_pricing, and list_apps. The verb is only implicit in the description (supplied by the title 'Read a blog article'), so it falls just short of the crispest verb+resource phrasing.

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?

'Get the slug from search' gives the agent the prerequisite and directly names the sibling tool that produces the required argument. It stops short of stating when-not to use this tool or what happens with an unknown slug, so there is no explicit exclusion guidance.

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