Skip to main content
Glama

how_to_in_app

Read-onlyIdempotent

Para lo que se hace en la app de Secondbrain y NO desde este chat: grabar una reunión (grabar_reunion), transcribir un audio (subir_audio), dictar al Diario (dictar), guardar páginas o mails (clipper), usar el bot de WhatsApp o Telegram (whatsapp_telegram), conectar el calendario (conectar_calendario), registrar la voz (mi_voz), conectar ClickUp o Jira (integraciones), compartir (compartir), subir archivos (archivos) o saber qué app instalar para qué y bajarla (instalar: la de escritorio para grabar reuniones, la del teléfono para los avisos, la extensión para los clips).

Devuelve por qué no se hace desde acá, los pasos, y los enlaces de descarga
que sirven para eso (iPhone, Android, Mac, Windows, web, extensión), con la
última versión. Usala en vez de decir «no puedo»: pasale los pasos y los
enlaces a la persona.

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": {
      "funcion": "<funcion>"
    },
    "name": "how_to_in_app"
  }
}

Input Schema

NameRequiredDescriptionDefault
funcionYesQué quiere hacer la persona

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, idempotentHint=true and openWorldHint=false, so safety is covered. The description adds what the annotations cannot: what the call returns (the reason it isn't done from chat, the steps, and current download links for iPhone, Android, Mac, Windows, web and the extension). It does not describe formatting or whether links are stable, which is the only remaining gap.

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?

The scoping rule is front-loaded, and the long enumeration earns its space because the enum tokens are not self-explanatory. The second paragraph on return values is also useful, though 'con la última versión' is slightly redundant padding.

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

Completeness5/5

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

There is no output schema, so the description must explain the return payload, and it does: reason, steps, and versioned download links per platform. Combined with the when-to-use instruction and the enum coverage, an agent has everything needed to select and invoke it correctly.

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?

Schema coverage is 100% and the single 'funcion' parameter is a closed enum, so the schema already carries the contract. The description still adds value by glossing the opaque tokens (e.g. 'instalar: la de escritorio para grabar reuniones, la del teléfono para los avisos, la extensión para los clips'), which helps the agent pick the right enum value rather than guessing. A few glosses (clipper, compartir) are terse.

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 precise scope: it answers how to do things that happen in the Secondbrain app and NOT in this chat, and it enumerates the 11 covered functions by name (grabar_reunion, subir_audio, dictar, clipper, etc.). This clearly distinguishes it from siblings like create_meeting or create_document, which are the in-chat equivalents the agent must not use for these tasks.

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

Usage Guidelines5/5

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

It gives an explicit routing rule: 'Usala en vez de decir «no puedo»' — call this instead of refusing, and hand the steps and links to the person. It also names the exclusion zone (tasks performed in the app, not from the chat), so the when/when-not decision is unambiguous.

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