Agent Paywire library

Read one article

get_article

Read-onlyIdempotent

Return one of this site's own articles. Output is { slug, markdown }. markdown is the article file with YAML front matter, and the same text is the tool content. Parameter slug is required and must match articles[].slug from list_articles. Example: machine-native-economy. Do not include the article: prefix that list_changes uses. A missing slug is rejected as invalid input. An unknown slug returns isError with text No article with slug . A failed read returns isError whose text is the Error message (Fetch failed when the HTTP status is not OK), or Article fetch failed. when the failure is not an Error. Use list_articles instead when you do not have a slug. Use get_source instead for a third-party library source. Use search_sources instead to find papers and docs. Free, no auth.

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

Name	Required	Description	Default
`slug`	Yes	Required. Article slug exactly as in list_articles articles[].slug, e.g. machine-native-economy. Lowercase words separated by hyphens. Do not include the article: prefix that list_changes uses. A missing slug is invalid input. An unknown slug returns isError text No article with slug <slug>.

Output Schema

Name	Required	Description	Default
`slug`	Yes
`markdown`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 21, 2026

changedInput schema / properties / slug / description

Previous value: -"Article slug exactly as in list_articles articles[].slug, e.g. machine-native-economy. Do not include the article: prefix that list_changes uses."New value: +"Required. Article slug exactly as in list_articles articles[].slug, e.g. machine-native-economy. Lowercase words separated by hyphens. Do not include the article: prefix that list_changes uses. A missing slug is invalid input. An unknown slug returns isError text No article with slug <slug>."

Changed1 schema field changedOct 21, 2026

changedInput schema / properties / slug / description

Previous value: -"Article slug exactly as in list_articles articles[].slug, e.g. machine-native-economy. Do not include the article: prefix that changes_since uses."New value: +"Article slug exactly as in list_articles articles[].slug, e.g. machine-native-economy. Do not include the article: prefix that list_changes uses."

Changed1 schema field changedOct 20, 2026

changedInput schema / properties / slug / description

Previous value: -"Article slug. Example: machine-native-economy."New value: +"Article slug exactly as in list_articles articles[].slug, e.g. machine-native-economy. Do not include the article: prefix that changes_since uses."

Changed2 schema fields changedOct 20, 2026

changedInput schema / properties / slug / description

Previous value: -"Article slug, for example machine-native-economy."New value: +"Article slug. Example: machine-native-economy."

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": false,
+  "properties": {
+    "markdown": {
+      "type": "string"
+    },
+    "slug": {
+      "type": "string"
+    }
+  },
+  "required": [
+    "slug",
+    "markdown"
+  ],
+  "type": "object"
+}

First observedOct 20, 2026

TDQS

A4.6/5.0

Behavior5/5

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

Annotations already cover read-only/idempotent/non-destructive, but the description goes further by enumerating failure modes: missing slug rejected as invalid input, unknown slug returns isError with 'No article with slug <slug>', and read failures return the underlying Error message. It also notes the markdown text equals the tool content, which the annotations do not convey.

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?

Front-loaded with purpose and output shape, then parameter rules, then error cases, then alternatives — a sensible ordering. It is on the long side and repeats error semantics already in the schema, but nearly every sentence carries distinct routing or failure information.

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?

For a single-parameter read tool with an output schema, annotations, and full schema coverage, the description supplies everything else an agent needs: output shape, slug provenance, error text, and alternative tools. Nothing material is missing.

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% and the slug property description already contains the format, the example, the 'article:' prefix caveat, and the error behavior — essentially duplicating the description. The description adds no syntax or meaning beyond the schema, so the baseline 3 applies.

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 ('Return one of this site's own articles') and immediately declares the return shape { slug, markdown }. It actively distinguishes itself from siblings get_source ('third-party library source'), search_sources, and list_articles, so an agent can route correctly without opening any 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?

Explicit routing rules: 'Use list_articles instead when you do not have a slug', 'Use get_source instead for a third-party library source', 'Use search_sources instead to find papers and docs'. It also states the precondition (slug must come from list_articles) and the cost/auth posture ('Free, no auth').

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

All Agent Paywire library tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?