Skip to main content
Glama

Kroel Graphics Docs

Listar páginas

list_pages
Read-onlyIdempotent

Lista las páginas del sitio de Kroel Graphics que se pueden leer en Markdown. Úsala primero para saber qué identificadores acepta read_page. Devuelve, por cada página, su identificador, título y URL.

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_pages"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
paginasYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, so the safety profile is covered. The description still adds real behavior: the scope is limited to pages readable in Markdown, and it states the per-page payload (identificador, título, URL). No auth or rate-limit detail, but nothing essential is missing for a read-only lister.

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 short sentences, front-loaded with the purpose, then the ordering advice, then the return shape. No filler and no repetition of the title or annotations.

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 and annotations cover the safety profile, so the remaining burden was purpose, workflow placement and return shape – all three are addressed. For a zero-parameter read-only lister feeding read_page, nothing an agent needs is absent.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool takes zero parameters, so there is no parameter semantics to explain and the baseline of 4 applies. The description does not waste words pretending otherwise.

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?

Names a specific verb plus a bounded resource ("las páginas del sitio de Kroel Graphics que se pueden leer en Markdown") and narrows the scope to Markdown-readable pages, which distinguishes it from a generic page listing and from read_page. An agent knows immediately what this returns.

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?

"Úsala primero para saber qué identificadores acepta read_page" gives an explicit ordering instruction and names the sibling it feeds into, so the agent knows this is a discovery step preceding read_page. It stops short of stating when not to call it (e.g., when an identifier is already known), which keeps it out of 5 territory.

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.