Skip to main content
Glama

Get article

get-article
Read-only

Get one article in full: title, slug, status, content_md (the Markdown body), meta description and published_urls. article_id comes from list-articles.

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": {
      "article_id": "<article_id>"
    },
    "name": "get-article"
  }
}

Input Schema

NameRequiredDescriptionDefault
article_idYesArticle ID from list-articles

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / article_id / description
      Previous value: -"Article ID"New value: +"Article ID from list-articles"
  2. Changed2 schema fields changed
    • removedInput schema / additionalProperties
      Removed value: -false
    • addedInput schema / properties / article_id / pattern
      Added value: +"^([0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[1-8][0-9a-fA-F]{3}-[89abAB][0-9a-fA-F]{3}-[0-9a-fA-F]{12}|00000000-0000-0000-0000-000000000000|ffffffff-ffff-ffff-ffff-ffffffffffff)$"
  3. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is covered. The description adds genuinely new context by enumerating the returned payload (content_md is the Markdown body, published_urls is a list) — meaningful because no output schema exists. It does not mention auth scoping or behavior on a missing article, which keeps it below 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?

Two sentences, no filler, and the highest-value information (what the full payload contains) is front-loaded before the ID provenance hint. Nothing could be deleted without losing signal.

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 field enumeration is the right compensating detail and makes the tool callable with confidence for a single-parameter read. Minor gaps remain — no mention of not-found/error behavior or whether content_md can be large/truncated — but nothing an agent strictly needs is missing.

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 single parameter is fully documented (uuid format, pattern, "Article ID from list-articles"). The description's restatement adds provenance but no new syntax or constraint detail, so this is baseline by the coverage rule.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

Names a specific verb and resource ("Get one article in full") and enumerates the returned fields, so the agent knows exactly what comes back. The contrast with list-articles is implicit in "one article" and made explicit by the ID-provenance note, distinguishing it from the list sibling.

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?

"article_id comes from list-articles" gives clear prerequisite/provenance guidance and routes the agent to the correct sibling to obtain the ID. It stops short of stating when not to use this tool (e.g., use list-articles for browsing multiple articles) or what happens for a stale/unknown ID.

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