Skip to main content
Glama

Listar secciones del sitio

listar_secciones
Read-onlyIdempotent

Listar áreas públicas y herramientas de AppInitDev.

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

Input Schema

NameRequiredDescriptionDefault
categoriaNoCategoria opcional para filtrar las secciones: todas, apps, articulos o herramientas.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / categoria / description
      Added value: +"Categoria opcional para filtrar las secciones: todas, apps, articulos o herramientas."
  2. First observed

TDQS

C2.4/5.0
Behavior2/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 fully covered. The description adds nothing beyond that: no indication of ordering, no note that results reflect the public site only, no hint about the shape or size of the returned list. With a one-line description it carries zero extra behavioral context.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

It is a single short sentence with no waste, so it is not verbose. However, the brevity stems from under-specification rather than tightness: the sentence front-loads a verb but leaves the core concept ('secciones') undefined.

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?

The tool is simple (one optional enum param), annotations are complete and there is no output schema to explain, so the low information load is partly justified. Still, an agent cannot predict what the returned list contains or how it relates to the sibling listing tools, which the description should have supplied.

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% and the single 'categoria' parameter has a fully documented enum (todas/apps/articulos/herramientas), so the schema does the work. The description does not mention the filter at all, meaning it adds no meaning beyond the schema — baseline 3 applies.

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

Purpose2/5

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

The description restates the title almost verbatim ('Listar secciones del sitio' → 'Listar áreas públicas y herramientas'), adding only the product name AppInitDev. It never defines what a 'sección' is or how it differs from the sibling listar_apps_desarrollador, listar_temas or listar_redes_sociales, so an agent cannot tell what domain this enumeration covers.

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 when-to-use statement, no mention of when to prefer a sibling such as listar_apps_desarrollador or buscar_apps, and no prerequisite context. The only implied guidance comes from the enum values in the schema, not from the description.

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.