Skip to main content
Glama
Sign In

api-evangelist

by com.apievangelist
OverviewDiscussionsAdmin

get_post

Read-only

One story by slug (YYYY-MM-DD-slug); include=["content"] returns the full markdown body.

Input Schema

NameRequiredDescriptionDefault
slugYesPost slug — date-prefixed, as find_posts returns it, e.g. "2026-09-29-you-cannot-see-your-own-api-from-the-outside".
contextNoOptional: why you are asking. One sentence — the task you are trying to complete, or what you expect to get back. Never included in the answer and never used to rank; it is read only when a result turns out to be wrong, which is when knowing the intent is what makes the report actionable.
includeNoPass ["content"] to inline the full body (Pro). Omitted, you get the summary.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / include / description
      Added value: +"Pass [\"content\"] to inline the full body (Pro). Omitted, you get the summary."
    • addedInput schema / properties / slug / description
      Added value: +"Post slug — date-prefixed, as find_posts returns it, e.g. \"2026-09-29-you-cannot-see-your-own-api-from-the-outside\"."
  2. Changed1 schema field changed
    • addedInput schema / properties / context
      Added value: +{
+  "description": "Optional: why you are asking. One sentence — the task you are trying to complete, or what you expect to get back. Never included in the answer and never used to rank; it is read only when a result turns out to be wrong, which is when knowing the intent is what makes the report actionable.",
+  "type": "string"
+}
  3. First observed

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already establish readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The one behavioral fact added — that omitting include yields the summary while ["content"] yields the full markdown body — is largely a restatement of the schema's own wording, so the description adds little new context (no not-found/error behavior, no rate or auth notes).

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 carrying the identifier format and the one behavioral toggle, with no filler. The payload/behavior split is immediately clear.

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 tells the agent what it will receive (summary vs full markdown body), which is the key decision point. It leaves unstated what happens on an unknown slug, but that is a minor gap for a tool of this 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 description coverage is 100%, so the baseline is 3. The description echoes the slug format and the include=["content"] behavior, but both are documented in the schema already, so it adds no meaning beyond it.

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+resource (get one story/post) and pins down the identifier format (YYYY-MM-DD-slug), which is enough to tell it apart from the plural find_posts. It stops short of naming the sibling explicitly, so the differentiation is inferable 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 Guidelines3/5

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

The slug-format hint implies 'use this once you already have a slug from find_posts', but the description never states when to choose this over find_posts or search tools, nor any prerequisites. Usage is only implied, not spelled out.

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

All api-evangelist toolsInspect
Try in Browser
Claude Code, inside the Godot 4 editorFlockbay puts an AI agent in the real Godot 4 editor: it writes GDScript, runs your game and fixes what breaks. Free, or bring your own Claude Code or Codex.flockbay.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources