Skip to main content
Glama

agent-tools (x402 + MCP + A2A directory)

get_article

Read-only

Read one published Blog article: metadata plus the full Markdown body.

Args:
    slug: The article slug, as returned by 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": {
      "slug": "<slug>"
    },
    "name": "get_article"
  }
}

Input Schema

NameRequiredDescriptionDefault
slugYesThe article slug, as returned by list_articles.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered and the description only needs to add context. It does add the useful constraint that only 'published' articles are readable, but says nothing about behavior on a missing or unpublished slug (error vs empty) and nothing about size or pagination of the Markdown body.

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?

Two short, front-loaded statements: purpose first, then the argument. It is appropriately sized for a one-parameter read tool, though the 'Args:' block duplicates the schema description verbatim and 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?

For a simple single-parameter read with an output schema and read-only annotations, this is nearly complete: the agent knows what it reads, what it returns, and where the slug comes from. The remaining gap is error/edge behavior for unknown or unpublished slugs, which matters given the 'published' qualifier.

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 single parameter is fully documented, so the schema does the heavy lifting; the description merely restates the same slug text. The only added nuance is provenance ('as returned by list_articles'), which the schema description already contains, so no meaning is added beyond the structured field.

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 and resource ('Read one published Blog article') and scopes it to published content, which implicitly separates it from the list_articles sibling referenced in the text. The return payload ('metadata plus the full Markdown body') is also stated, so an agent knows exactly what it gets.

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?

Usage is implied rather than stated: the slug note ('as returned by list_articles') hints at the correct workflow of listing first, then fetching. There is no explicit when-to-use versus when-not statement, no mention of what happens for draft or unpublished slugs, and no alternative tool named.

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.