Skip to main content
Glama

get_guide

Read-onlyIdempotent

La guía pública de Secondbrain (secondbrain.media/guide): cómo funciona cada parte —el Diario, las tareas, los recaps de reuniones, el Atlas, el calendario, Teams, el bot de WhatsApp y Telegram, el clipper, este MCP— y las descargas. No trae la página de precios: para eso, el sitio.

Para preguntas sobre el PRODUCTO (qué es, cómo se usa, qué hace), no sobre
los datos de la persona. Devuelve las secciones que mejor
contestan, con su texto, su enlace (url) y sus piezas visuales —capturas,
videos y diagramas de la guía—, más otras secciones cercanas. Con
`seccion` trae una sección exacta por su clave (pagina#seccion).

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

Input Schema

NameRequiredDescriptionDefault
idiomaNoIdioma de la conversación
seccionNoClave exacta de una sección (p. ej. "recaps#grabar"), de una respuesta anterior
preguntaNoLo que se quiere saber, con las palabras de la persona

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent and non-destructive, so the safety profile is covered. The description adds genuinely new behavior: it returns the best-matching sections with their text, url and visual assets (screenshots, videos, diagrams) plus nearby sections, and it discloses the pricing-page gap — none of which is in the structured fields.

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?

Four short sentences, front-loaded with what the guide is, then the scope exclusion, then the return shape. The enumeration of product areas is long but earns its place by telling the agent what topics are answerable.

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?

With no output schema, the description correctly compensates by describing the return payload (matching sections, text, url, media, nearby sections). Parameters are fully documented in the schema and the scope exclusion is explicit; only the interaction between the two input modes is left implicit.

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%, so each parameter is already documented, including the `pagina#seccion` key format. The description restates the `seccion` fetch mode rather than adding syntax, defaults, or precedence rules (e.g. what happens if both `pregunta` and `seccion` are supplied), so the schema does the heavy lifting.

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?

The description states a specific resource ("La guía pública de Secondbrain") and enumerates the product areas it covers (Diario, tareas, recaps, Atlas, calendario, Teams, bots, clipper, this MCP), so an agent knows exactly what corpus this tool answers from and can distinguish it from the data-oriented siblings.

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?

It gives a clear negative condition — use for PRODUCT questions, not for the person's data — and an explicit exclusion (pricing page is not included; "para eso, el sitio"). It stops short of naming a concrete sibling tool to use instead for data questions, so the routing is implied rather than fully resolved.

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.

Resources