Skip to main content
Glama

Fmind Freelance AI Architect Website

Read an article

get_article
Read-only

Read a public article's complete Markdown, dates, canonical URL, and hosted section links. Use a slug from search_articles; unknown and draft articles are unavailable.

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
slugYespublic article slug from search_articles or list_publications

Output Schema

NameRequiredDescriptionDefault
articleYes
markdownYes
sectionsYes
canonical_urlYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changed
    • addedInput schema / properties / slug / description
      Added value: +"public article slug from search_articles or list_publications"
    • addedOutput schema / $defs / ArticleSectionLink
      Added value: +{
      +  "properties": {
      +    "title": {
      +      "title": "Title",
      +      "type": "string"
      +    },
      +    "url": {
      +      "title": "Url",
      +      "type": "string"
      +    }
      +  },
      +  "required": [
      +    "title",
      +    "url"
      +  ],
      +  "title": "ArticleSectionLink",
      +  "type": "object"
      +}
    • addedOutput schema / properties / sections / items / $ref
      Added value: +"#/$defs/ArticleSectionLink"
    • removedOutput schema / properties / sections / items / additionalProperties
      Removed value: -{
      -  "type": "string"
      -}
    • removedOutput schema / properties / sections / items / type
      Removed value: -"object"
  2. Changed2 schema fields changed
    • removedOutput schema / $defs / ArticleSummary / properties / canonical
      Removed value: -{
      -  "default": "",
      -  "title": "Canonical",
      -  "type": "string"
      -}
    • removedOutput schema / $defs / ArticleSummary / properties / syndicated
      Removed value: -{
      -  "default": "",
      -  "title": "Syndicated",
      -  "type": "string"
      -}
  3. Changed1 schema field changed
    • addedInput schema / additionalProperties
      Added value: +false
  4. Added

TDQS

A4/5.0
Behavior4/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 description adds the meaningful failure mode that draft and unknown slugs are unavailable, which is exactly the kind of error behavior an agent needs before calling. It does not describe size limits or latency, but that is minor against the annotation coverage.

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, front-loaded with what is returned and followed by the identifier rule and failure condition. Nothing is redundant and no sentence could be dropped without losing information.

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 an output schema present and a single required parameter, the description covers the essential call contract: what the identifier is, where it comes from, what is returned, and what happens on bad input. Only edge details such as slug formatting guidance are left entirely to the schema.

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 schema already documents the slug plus its pattern and length bounds, so the baseline is 3. The description adds only the sourcing hint ('from search_articles'), which partially duplicates the schema's own note and actually narrows it, since the schema also allows list_publications.

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?

Names a specific verb and resource ('Read a public article') and enumerates the payload ('complete Markdown, dates, canonical URL, and hosted section links'), which is far more concrete than the title. It also points to search_articles as the source of the slug, implicitly separating lookup from read, though it never explicitly contrasts itself with fetch-style siblings.

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?

Gives a clear prerequisite ('Use a slug from search_articles') and an explicit exclusion ('unknown and draft articles are unavailable'), so the agent knows which identifiers are valid. It stops short of naming an alternative tool for cases where the article is a draft or non-public, so the fallback path is left to inference.

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