Skip to main content
Glama

Leer articulo publicado

obtener_articulo
Read-onlyIdempotent

Recuperar texto público de un artículo de AppInitDev listado en el catálogo y devolver la fuente original; puede limitar longitud.

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": {
      "url": "<url>"
    },
    "name": "obtener_articulo"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYesURL HTTPS canonica de un articulo listado en el catalogo publico appinitdev.com.
max_caracteresNoLongitud maxima del texto devuelto, entre 500 y 16000 caracteres (predeterminado: 12000).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / max_caracteres / description
      Added value: +"Longitud maxima del texto devuelto, entre 500 y 16000 caracteres (predeterminado: 12000)."
    • addedInput schema / properties / url / description
      Added value: +"URL HTTPS canonica de un articulo listado en el catalogo publico appinitdev.com."
  2. First observed

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive and closed-world, so the safety profile is covered. The description adds that it returns the original source and that length can be limited, but says nothing about error behavior for non-catalog URLs or about truncation semantics when the limit is hit.

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?

One compact sentence with the core action front-loaded and the optional length control mentioned last. It is efficient, though the trailing 'puede limitar longitud' is slightly clipped and could be clearer about the default behavior.

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

Completeness3/5

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

For a simple two-parameter read tool with full schema coverage and complete annotations, the description covers the essentials. It leaves 'fuente original' underspecified — whether that means raw HTML, canonical URL, or extracted text — which matters for an agent deciding whether this tool answers its need.

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 both parameters (url and max_caracteres) are already fully documented in the schema with bounds and defaults. The description's 'puede limitar longitud' merely echoes max_caracteres without adding new meaning, so the baseline of 3 applies.

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 ('Recuperar') and resource ('texto público de un artículo de AppInitDev'), plus the return shape ('devolver la fuente original'). It does not name or distinguish itself from plausible siblings such as buscar_texto_completo or buscar_conocimiento, so it stops short of a 5.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The phrase 'listado en el catálogo' implies a precondition (the article must already be indexed in the public catalog), which is useful implied guidance. However, there is no explicit when-to-use versus alternatives, and no statement of what to do if the article is not in the catalog.

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.