Agent Paywire library

Read one article

get_article

Read-onlyIdempotent

Return one Agent Paywire article as Markdown with YAML front matter, by slug. Get slugs from list_articles, or from changes_since after removing the article: prefix. Use get_source instead for third-party library sources, which are not articles. An unknown slug returns an isError result (No article with slug ...). Free, no auth.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`slug`	Yes	Article slug exactly as in list_articles articles[].slug, e.g. machine-native-economy. Do not include the article: prefix that changes_since uses.

Output Schema

TableJSON Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

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.7/5.0

Behavior5/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, openWorld), so the description is free to add the traits that matter here: the exact output shape (Markdown + YAML front matter), the failure behavior (unknown slug yields an isError result containing 'No article with slug ...'), and the auth/cost model (free, no auth). That is meaningful disclosure beyond structured data.

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?

Three tight sentences, front-loaded with the core behavior and then proceeding to acquisition, disambiguation, and edge case. Each sentence carries distinct information with no restatement padding.

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?

An output schema exists, so return values need not be enumerated, yet the description still states the serialization format. Combined with slug acquisition, the sibling disambiguation, the error case, and the no-auth note, everything needed to call this correctly on the first attempt is present.

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 there is a single parameter, so the schema already defines slug, its format example, and the 'no article: prefix' rule. The description restates the prefix caution but adds no syntax or format detail the schema lacks, 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 (Return) and resource (one Agent Paywire article) plus the exact serialization format (Markdown with YAML front matter) and the keying mechanism (by slug). It also explicitly names what it is not: get_source is for third-party library sources, and list_articles/changes_since are the slug sources, so an agent can route correctly without opening sibling schemas.

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?

Gives both when-to-use paths and their prerequisites: slugs come from list_articles[].slug or from changes_since after stripping the article: prefix. It also names the explicit alternative (get_source) and the condition that selects it (third-party library sources). Nothing about selection 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.

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?