Skip to main content
Glama

Ahmed Shaikh's Blog

Read a blog post

get_post
Read-onlyIdempotent

Returns one post in full as Markdown, including its FAQ section. Pass the slug from search_posts / list_posts, or the post's URL.

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
slugYesPost slug (e.g. "what-is-ransomware") or full post URL.

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, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety and repeat-call profile is covered. The description adds genuinely new behavior detail: the body is returned in full as Markdown and includes the FAQ section. It says nothing about behavior for a non-existent slug or about pagination/truncation of long posts.

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 filler: the return shape leads, the input sourcing follows. Every clause carries information the agent can act on.

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 no output schema, the description supplies the essentials an agent needs: what comes back (full post, Markdown, FAQ included) and how to supply the slug. Only the failure mode for an invalid or unknown slug is left unaddressed, which is a minor gap given the annotations already mark this as a safe, idempotent read.

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%, and the schema already documents both accepted forms of the slug (slug text or full post URL) with an example and length bounds. The description's main added value is provenance, telling the agent to obtain the slug from search_posts or list_posts, but it restates the URL option the schema already covers. Baseline 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?

States a specific verb and resource ('Returns one post in full as Markdown') plus the extra payload detail of the FAQ section, which clearly contrasts with the multi-result siblings list_posts and search_posts. It stops short of naming those siblings as explicit alternatives, so differentiation is implied rather than stated.

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?

Tells the agent where the slug comes from ('Pass the slug from search_posts / list_posts, or the post's URL'), which effectively positions this as the follow-up retrieval step after a search or list. It does not state a when-not condition, e.g. what to do if the slug is unknown or the post is missing.

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