Skip to main content
Glama
Sign In
uleszka

uleszka

by jokerwader
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Czytaj artykuł

read_article
Read-only

Retrieves the full original text of an archived article as Markdown by ID or title, split into parts when long. Use it to read and verify complete article content in conversation.

Instructions

Returns the full original text of an article as Markdown (verbatim). Long articles are split into parts of ~15000 characters – read all parts to see the whole text. Images appear as Markdown image links with repository paths, each followed by an AI description in [opis AI: …] (not part of the original); use get_image to view one. Links to other articles appear as artykul:.

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": {
      "id": "<id>"
    },
    "name": "read_article"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesid artykułu (z list_articles/search) albo jego tytuł
partNoNumer części (od 1)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.2.0

TDQS

A4.7/5.0
Behavior5/5

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

Annotations only declare readOnlyHint=true, and the description adds substantial behavior: chunking at ~15000 characters with a requirement to read every part, how images are rendered with repository paths and inline [opis AI: …] descriptions that are not original content, and how internal links are encoded as artykul:<id>. These are exactly the traits an agent needs and could not infer from structured fields.

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?

Four compact sentences, each carrying distinct load: return format, pagination rule, image rendering, link encoding. The primary behavior is front-loaded and there is no filler.

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?

No output schema exists, and the description compensates fully by describing the returned Markdown, its part-based splitting, and the conventions embedded in image links and article links. An agent can consume the result correctly without further guidance.

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% (both id and part are documented), so the baseline is 3; the description earns above that by explaining the ~15000-character part size and the obligation to read all parts, which gives real meaning to the `part` parameter beyond its schema text.

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 ('Returns the full original text of an article as Markdown (verbatim)') and pins down the exact return format, which cleanly separates it from siblings like find_in_article (search within text), read_book, and get_image.

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 explicit routing for one case ('use get_image to view one') and implies the use case of reading whole article text, including the instruction to read all parts. It does not explicitly say when to prefer this over find_in_article or search, so it stops short of full when/when-not coverage.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools