Skip to main content
Glama

bienvenida

Read-onlyIdempotent

Dibuja la bienvenida de una cuenta NUEVA: la tarjeta con las tres preguntas para dejar armado su workspace (cómo se llama, para qué lo va a usar, qué quiere hacer primero). Se contesta tocando, no escribiendo.

Llamala UNA vez, antes que cualquier otra cosa, cuando el Secondbrain esté vacío (las instrucciones del servidor lo dicen). Si ya se hizo, devuelve por dónde seguir y no dibuja el formulario.

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

Input Schema

NameRequiredDescriptionDefault
idiomaNoIdioma de la persona (default: es)
workspace_idNoUUID del workspace, o su nombre tal como lo dice el usuario ('Acme', 'el personal'). Omitir si el token ya tiene workspace fijo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations cover the safety profile (readOnly, idempotent, non-destructive, closed world), and the description adds genuinely new context: the output is an interactive card answered by tapping rather than typing, and a repeat call returns a continuation pointer instead of re-rendering. It does not describe what the returned pointer looks like, but no output schema exists so that is partly expected.

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?

Front-loaded with the core action and card contents, then the calling condition and the already-done behavior. The parenthetical '(las instrucciones del servidor lo dicen)' is slightly redundant but short, and three sentences carry no filler.

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 zero-required-parameter onboarding tool with no output schema, the description's account of the return-on-repeat behavior is the most valuable missing piece, and it is only implied. Overall adequate, but it does not spell out what the agent should do after a repeat call returns the continuation pointer.

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 descriptions already cover both parameters at 100%, including the default for 'idioma' and the accepted forms of 'workspace_id'. The description adds nothing about parameter 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 concrete verb and object ('Dibuja la bienvenida de una cuenta NUEVA') and describes what the card contains: three questions about name, purpose and first action. It does not explicitly differentiate itself from similarly themed siblings such as configurar_workspace, so it falls 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 Guidelines4/5

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

Gives a clear condition ('cuando el Secondbrain esté vacío'), timing ('antes que cualquier otra cosa') and frequency ('Llamala UNA vez'), plus what to expect on a repeat call. It names no alternative tool for the case where the agent might reach for a different onboarding/config tool, so no exclusions.

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