Skip to main content
Glama

Get content

get_content
Read-onlyIdempotent

Read an article, news story or opinion piece, with its citation.

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": {
      "type": "<type>",
      "slug": "<slug>"
    },
    "name": "get_content"
  }
}

Input Schema

NameRequiredDescriptionDefault
slugYesURL slug of the record, as returned by a search tool, for example "acme-cloud".
typeYesKind of editorial content: article, news or opinion.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / slug / description
      Added value: +"URL slug of the record, as returned by a search tool, for example \"acme-cloud\"."
    • addedInput schema / properties / type / description
      Added value: +"Kind of editorial content: article, news or opinion."
  2. First observed

TDQS

B3.3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=true, so the safety profile is covered. The description adds that a citation is returned alongside the content, which is genuinely new information, but it says nothing about full-text length, pagination, or failure behavior for a missing slug.

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?

A single short sentence with zero filler; the resource and the citation payload are both front-loaded, and nothing is repeated from the title or annotations.

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

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple two-parameter read tool with full schema coverage and rich annotations, most of what an agent needs is present. However, with no output schema, the description should clarify that the article body plus citation is the return payload — 'with its citation' only partially does that, and nothing indicates whether the full text or a summary is returned.

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%, so both parameters (slug format and the article/news/opinion enum) are already fully documented in the schema. The description restates the three content kinds without adding format, sourcing, or slug-derivation detail beyond what the schema provides, so the baseline of 3 applies.

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 ('Read') and resource ('an article, news story or opinion piece'), and the enumeration mirrors the type enum so an agent knows what entity is fetched. It does not explicitly differentiate itself from the sibling search_content beyond the 'read vs search' verb contrast.

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

Usage Guidelines2/5

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

No when-to-use guidance is given: it never says to call search_content first to obtain a slug, nor when to prefer this over fetch or search. The only hint is in the schema's slug description, not in the tool description itself.

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