Skip to main content
Glama

Kroel Graphics Docs

Leer página

read_page
Read-onlyIdempotent

Devuelve el contenido completo en Markdown de una página de Kroel Graphics. Úsala cuando necesites el detalle de servicios, clientes, trayectoria, contacto o privacidad. Devuelve el identificador, la URL y el texto en Markdown.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "pagina": "<pagina>"
    },
    "name": "read_page"
  }
}

Input Schema

NameRequiredDescriptionDefault
paginaYesIdentificador de la página (ver list_pages).

Output Schema

NameRequiredDescriptionDefault
urlNo
paginaYes
markdownYesContenido de la página.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / pagina / enum
      Previous value: -[
      -  "index",
      -  "about",
      -  "contact",
      -  "faq",
      -  "auth",
      -  "privacy",
      -  "developers"
      -]New value: +[
      +  "index",
      +  "about",
      +  "contact",
      +  "pricing",
      +  "faq",
      +  "auth",
      +  "privacy",
      +  "developers"
      +]
  2. First observed

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is fully covered. The description adds only that the response contains identifier, URL and Markdown text, which is largely redundant with the output schema; no error behavior for invalid identifiers is described.

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?

Three short sentences, front-loaded with the core action before the usage hint. Minor redundancy in restating the Markdown return format twice.

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?

An output schema exists, so return values need not be explained, and the single enum parameter is well documented. For such a simple read tool the definition is essentially complete; only edge-case behavior for an out-of-range identifier is unaddressed.

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% with an enum of page identifiers and a pointer to list_pages, so the schema carries the parameter semantics. The description adds no format, default, or resolution detail beyond it.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource: returns the full Markdown content of a Kroel Graphics page. The scope (single page by identifier) is unambiguous, though it never names list_pages or search_docs to contrast with 'get one page detail' vs 'list' or 'search'.

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 cuando necesites el detalle de servicios, clientes, trayectoria, contacto o privacidad' gives concrete usage context tied to the content topics. It lacks explicit exclusions or a pointer to the alternative tools for listing/searching, so the agent must infer that boundary.

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.