Skip to main content
Glama

Get article

get_article
Read-onlyIdempotent

Get one published article by exact slug, including full text, sources, author, dates and any sponsorship disclosure. Discover its slug with search or list_articles first. Unknown or unpublished slugs return a not-found error; use search for discovery, list_articles for recent summaries.

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

Input Schema

NameRequiredDescriptionDefault
slugYesExact article slug returned by search or list_articles; copy it rather than guessing. Use the lowercase hyphenated identifier (1-120 characters), not a title or full URL.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / slug / description
      Added value: +"Exact article slug returned by search or list_articles; copy it rather than guessing. Use the lowercase hyphenated identifier (1-120 characters), not a title or full URL."
  2. First observed

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description still adds real context: only published articles are retrievable and a not-found error is the outcome for unknown/unpublished slugs. It stops short of describing response size or rate limits, so not 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?

Three sentences, zero filler: payload first, discovery path second, error/alternative routing third. Front-loaded with the operation before the caveats.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/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 compensates by naming the returned fields and documenting the error case. An agent has everything needed to call it correctly on the first attempt.

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 the slug property already documents the pattern, length bounds and the 'copy it, don't guess' instruction. The description's only addition is the emphasis on 'exact slug', which largely restates the schema. Baseline 3 applies 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.

Purpose5/5

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

States a specific verb and resource ('Get one published article by exact slug') and enumerates the payload returned (full text, sources, author, dates, sponsorship disclosure). The word 'published' and the singular-resource framing clearly separate it from list_articles and search.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

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

Explicitly routes discovery to 'search or list_articles first' and differentiates the two alternatives by intent: 'use search for discovery, list_articles for recent summaries.' It also states the failure condition (unknown or unpublished slug returns not-found), which tells the agent when not to use it.

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