Skip to main content
Glama

Get Article

get_article
Read-onlyIdempotent

Full machine-readable article (the JSON twin: facts, sources, call, full text). Use search_articles or get_latest first if you do not have a slug. Returns the article's complete JSON twin exactly as published — headline, summary, key facts, sources, the call the article makes (if any), and the full text. The slug must be lowercase letters, digits, and hyphens; an unknown or malformed slug returns an error, never a partial result. Behaviour: read-only and public — no authentication or API key; served from the site's published article files, and every call is logged in aggregate (tool name, query, result count, coarse client class; no IP addresses).

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
slugYesArticle slug, as returned by search_articles or get_latest, e.g. institutions-sold-the-dip.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / slug / description
      Previous value: -"Article slug, e.g. institutions-sold-the-dip."New value: +"Article slug, as returned by search_articles or get_latest, e.g. institutions-sold-the-dip."
  2. First observed

TDQS

A4.8/5.0
Behavior5/5

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

Beyond the annotations (readOnly, idempotent, non-destructive, closed-world), it discloses that no authentication or API key is needed, that content is served from the site's published article files, and that calls are logged in aggregate with a specific field list and the explicit note that no IP addresses are recorded. It also specifies failure behavior — an unknown or malformed slug returns an error, never a partial result — which is exactly the kind of behavioral contract annotations cannot express.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The content is dense and front-loaded, leading with the payload then the precondition, with the logging disclosure correctly placed last. There is mild redundancy in restating the field list ('JSON twin' then 'complete JSON twin … headline, summary, key facts, sources, the call, full text'), but nothing that obscures the key points.

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?

With a single required parameter and no output schema, the description carries the full burden and does so: it covers input format, failure mode, auth requirements, data source, and return contents. Nothing an agent needs to call this correctly is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% and the schema already gives an example slug, so the baseline is 3. The description goes beyond it by constraining the slug to lowercase letters, digits, and hyphens and by tying malformed input to an error outcome, adding genuine meaning about accepted values.

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?

The description opens with a specific verb and resource — a full machine-readable article retrieved by slug — and immediately enumerates what it contains (facts, sources, call, full text). It also names search_articles and get_latest as the discovery tools, so an agent can distinguish it from siblings without opening a schema.

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?

It states the precondition explicitly: use search_articles or get_latest first if you do not have a slug. That is a clear when-to-use routing rule with named alternatives rather than an implied one.

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.