Skip to main content
Glama

Listar temas del indice

listar_temas
Read-onlyIdempotent

Lista la clasificación automática y la cobertura de la búsqueda; las etiquetas son heurísticas, no revisiones editoriales.

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": "listar_temas"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and closed-world scope, so the safety profile is covered. The description adds a genuinely useful data-quality caveat that annotations cannot express: the tags are heuristic rather than editorial review, which tells the agent how much to trust the labels.

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?

A single compact sentence with the verb front-loaded and no filler. The trailing caveat earns its place, though "cobertura de la búsqueda" is left unqualified and reads slightly cryptic without context.

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?

With no parameters, no output schema and rich annotations, the description only needs to explain what the listing contains. It says classification and search coverage are returned and flags label reliability, but does not indicate shape, ordering, or what "cobertura" measures.

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 the schema carries no semantics for the description to supplement. Baseline of 4 applies; nothing about the empty schema is misrepresented.

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?

"Lista" plus the resources it returns ("clasificación automática", "cobertura de la búsqueda", "etiquetas") gives a concrete verb and object, matching the title's "temas del índice". It is not differentiated from siblings such as listar_secciones or resumen_catalogo, which could plausibly return overlapping index metadata.

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

Usage Guidelines2/5

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

There is no explicit when-to-use statement, no prerequisites, and no routing to alternatives like listar_secciones or estado_indice. Usage is only inferable from the fact that it exposes classification and coverage.

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.