Skip to main content
Glama

Pay2GPT

List guides and articles

list_articles
Read-onlyIdempotent

List Pay2GPT's how-to guides (ordering, paying, connecting a ChatGPT account, renewing) and blog articles in one language, each with its title, page URL and Markdown URL. Pass a URL to read_page for the full text.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_articles"
  }
}

Input Schema

NameRequiredDescriptionDefault
localeNoLanguage of the list: zh-CN (default), en or ru
sectionNoguide, blog or all (default)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint=false and destructiveHint=false, so the safety profile is covered. The description adds real value beyond them by disclosing the return payload shape (title, page URL, Markdown URL) and the single-language scoping of results. It does not cover pagination, result limits, or ordering, which is why this is not higher.

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?

Two sentences, front-loaded with the verb and resource, then the returned fields, then the handoff instruction. No filler or restated title text.

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, so the description carries the burden of describing return values, and it does so precisely (title, page URL, Markdown URL). Combined with the read_page handoff and 100% schema coverage, an agent has everything needed to call it correctly.

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% and both parameters have enum descriptions, so the schema does the heavy lifting. The phrase 'in one language' adds the key implication that the locale scopes the whole result set rather than filtering individual items. Nothing is said about how locale interacts with section.

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 ('List Pay2GPT's how-to guides ... and blog articles'), enumerates the covered topics, and names the returned fields (title, page URL, Markdown URL). It is clearly distinguishable from read_page, which is named as the follow-up for full text.

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?

The definition establishes the workflow position: list here, then pass a returned URL to read_page for full text. That is a concrete usage rule with an explicit alternative. It does not spell out when to pick section=guide vs blog vs all, but that choice is documented in the schema enums.

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