Skip to main content
Glama

agent-tools (x402 + MCP + A2A directory)

list_articles

Read-only

List published Blog articles, newest first (metadata only).

Args:
    query: Optional words to match in title, summary or body.
    tag: Optional tag to filter by.
    page: Page number, 20 articles per page.

Use get_article(slug) for the full Markdown body.

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
tagNoOptional tag to filter by.
pageNoPage number, 20 articles per page.
queryNoOptional words to match in title, summary or body.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnlyHint=true, openWorldHint=false), and the description adds real behavior beyond them: only published articles are returned, ordering is newest-first, results are metadata-only without body content, and pagination is fixed at 20 per page. It stops short of describing what metadata fields come back or total-count/pagination limits, but the output schema covers the return shape.

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?

The key scoping sentence is front-loaded and wastes nothing. The Args block is partly redundant with a 100%-covered schema, but it is short and the closing sibling pointer earns its place.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a zero-required-parameter read-only listing tool with an output schema, the description covers what an agent needs: published-only scope, ordering, metadata-only nature, page size, and the alternative for full content. Return structure is correctly left to the output schema; only pagination limits and filter-combination behavior are left implicit.

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%, so all three parameters are already documented in the schema at the same level of detail. The Args block largely restates those descriptions verbatim ('match in title, summary or body', '20 articles per page'), adding no new syntax, defaults, or interaction semantics such as how query and tag combine. Baseline 3 applies when the schema does the work.

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 published Blog articles'), plus scope qualifiers that matter for selection: only published items, newest-first ordering, and metadata-only results. It also names the sibling (get_article) that serves the other need, so an agent can distinguish the two without opening schemas.

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?

Explicitly routes the agent to get_article(slug) when the full Markdown body is needed, which is the main ambiguity for a listing tool. It does not spell out when-not to use it (e.g. no pagination-limit or empty-result advice), so it falls short of the exhaustive when/when-not/alternatives bar.

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.