Skip to main content
Glama

Get blog post

get_blog_post
Read-onlyIdempotent

One blog post as plain text, by slug from list_blog_posts, with its FAQ and related course slugs.

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
langNoLanguage of the answer: en, de or sr. Default en.en
slugYesThe slug as another tool returned it

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 cover the safety profile (readOnly, idempotent, non-destructive, closed world), so the bar is lower. The description still adds useful non-annotation context: the response is plain text and includes FAQ plus related course slugs, which is the main behavioral fact an agent needs. It does not say what happens when the slug is unknown, keeping it off a 5.

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 sentence with zero filler, and the payload content (FAQ, related course slugs) is front-loaded alongside the format. Nothing could be removed without losing information.

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 only two parameters, full schema coverage, and annotations declaring the safety profile, the missing piece is return-value shape – and the description partially covers that by naming FAQ and related course slugs. A brief note on missing-slug behavior would make it fully complete.

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%, so both parameters are already documented, and the description adds only the provenance constraint on 'slug' (it must come from another tool's output). The 'lang' parameter is left entirely to the schema. Baseline 3 is appropriate when the schema does the heavy lifting.

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 states a specific resource ('One blog post') and its return format ('as plain text'), then names the payload extras the caller gets ('its FAQ and related course slugs'). It also distinguishes itself from the list-level sibling by pointing at 'list_blog_posts' as the slug source, though it does not contrast with get_page/get_course.

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 rather than stated: the 'slug from list_blog_posts' phrasing tells the agent to enumerate first, and 'The slug as another tool returned it' in the schema reinforces that. There is no explicit when-not guidance and no stated behavior for a slug that doesn't match a post.

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