Skip to main content
Glama

Agent Paywire library

by com.agentpaywire
OverviewDiscussionsAdmin

List newest library sources

latest_sources
Read-onlyIdempotent

Return the newest third-party library sources, sorted by date_published descending, with undated sources last. category keeps one category (ids from list_categories) before limit is applied; limit caps rows at 1-50 (default 10). There is no offset or cursor, and count is the rows returned, not the library total. Use changes_since to sync everything changed after a date, including articles, datasets and bots; use search or search_library for text, tag or type filters. Free, no auth.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoMaximum rows to return, 1-50, default 10. Values above 50 are rejected, and there is no offset to page further.
categoryNoOptional category id from list_categories, e.g. bitcoin-lightning. Filters before the limit is applied; omit for all categories.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
countYes
sourcesYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / category / description
      Previous value: -"Category id. Example: bitcoin-lightning."New value: +"Optional category id from list_categories, e.g. bitcoin-lightning. Filters before the limit is applied; omit for all categories."
    • changedInput schema / properties / limit / description
      Previous value: -"Maximum rows, from 1 to 50. Example: 10. Default 10."New value: +"Maximum rows to return, 1-50, default 10. Values above 50 are rejected, and there is no offset to page further."
  2. Changed6 schema fields changed
    • changedInput schema / properties / category / description
      Previous value: -"Optional category id."New value: +"Category id. Example: bitcoin-lightning."
    • addedInput schema / properties / category / enum
      Added value: +[
+  "bitcoin-lightning",
+  "payments",
+  "agent-protocols",
+  "robotics-autonomy",
+  "iot",
+  "datasets-benchmarks",
+  "safety-security",
+  "regulation"
+]
    • changedInput schema / properties / limit / description
      Previous value: -"Maximum results, 1 to 50. Default 10."New value: +"Maximum rows, from 1 to 50. Example: 10. Default 10."
    • addedInput schema / properties / limit / maximum
      Added value: +50
    • addedInput schema / properties / limit / minimum
      Added value: +1
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": false,
+  "properties": {
+    "count": {
+      "type": "integer"
+    },
+    "sources": {
+      "items": {
+        "additionalProperties": true,
+        "properties": {
+          "authors": {
+            "items": {
+              "type": "string"
+            },
+            "type": "array"
+          },
+          "category": {
+            "type": "string"
+          },
+          "date_published": {
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "featured": {
+            "type": "boolean"
+          },
+          "id": {
+            "type": "string"
+          },
+          "publisher": {
+            "type": "string"
+          },
+          "summary": {
+            "type": "string"
+          },
+          "tags": {
+            "items": {
+              "type": "string"
+            },
+            "type": "array"
+          },
+          "title": {
+            "type": "string"
+          },
+          "type": {
+            "type": "string"
+          },
+          "url": {
+            "type": "string"
+          },
+          "verified_at": {
+            "type": "string"
+          }
+        },
+        "required": [
+          "id",
+          "title",
+          "publisher",
+          "authors",
+          "date_published",
+          "url",
+          "type",
+          "category",
+          "summary",
+          "tags",
+          "verified_at"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    }
+  },
+  "required": [
+    "count",
+    "sources"
+  ],
+  "type": "object"
+}
  3. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already cover readOnly/idempotent/destructive/openWorld, so the bar is lower, yet the description still adds non-obvious operational traits: no offset or cursor, count is rows returned rather than library total, and no auth/free access. Sort ordering and undated-last behavior are also disclosed. It stops short of rate limits or error behavior, so not a full 5.

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?

A single dense paragraph with purpose and sort order front-loaded, then parameters, then pagination caveats, then routing to alternatives. Nearly every clause earns its place, though the middle sentences are tightly packed and could be split for scanability.

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 no explanation, and the description still covers the essentials an agent needs: defaults and bounds, filter-before-limit interaction, absence of paging, count semantics, auth requirements, and which sibling to pick instead. Nothing material is missing for a two-parameter read tool.

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%, so the schema already documents limit (1-50, default 10) and category (enum ids from list_categories, filter applied before limit). The description largely restates those facts ('category keeps one category before limit is applied; limit caps rows at 1-50'), adding only mild emphasis on the singular-category semantics. Baseline 3 applies when the schema does the heavy lifting.

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 the newest third-party library sources') plus the ordering ('sorted by date_published descending, with undated sources last'). It also distinguishes itself from siblings by explicitly naming changes_since, search and search_library as the tools for different needs.

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 explicit routing: use changes_since to sync everything changed after a date, use search/search_library for text, tag or type filters, and this tool for the newest sources. The condition that selects each alternative is spelled out, leaving nothing 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 toolsInspect
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