Skip to main content
Glama

configurar_workspace

Destructive

Deja armado el workspace de una cuenta nueva con lo que la persona contestó en la bienvenida: lo renombra (si es dueño o admin), guarda para qué lo usa y qué quiere hacer primero, y escribe una primera nota de bienvenida en el Diario de hoy.

La tarjeta de bienvenida la llama sola. Llamala vos sólo si el cliente no dibuja tarjetas y la persona te contestó por escrito.

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

Input Schema

NameRequiredDescriptionDefault
usoNopersonal | trabajo | estudio | equipo
focoNoQué quiere hacer primero: notas, tareas, reuniones, calendario
idiomaNoIdioma de la persona (default: es)
nombreNoCómo quiere llamar a su espacio
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

A4.2/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true and readOnlyHint=false, and the description adds real value beyond them: it discloses the permission gate (rename only if owner or admin) and the concrete side effect of creating a welcome note in today's Journal. It does not discuss idempotency or what happens if it is run twice on the same workspace, which is the main remaining gap for a non-idempotent mutation.

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

Conciseness5/5

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

Two tight paragraphs: the first front-loads the effects, the second front-loads the invocation rule. No filler, no repetition of the name, and the conditional permission note is embedded inline rather than expanded into its own sentence.

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?

Covers what the tool changes, who may trigger the rename, and when to call it, which is the full burden for an optional-parameter mutation with no output schema. Minor omission: no indication of what the agent should report back or what state changes if the person skipped some welcome answers.

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 the schema already documents all five parameters including the enum and the workspace_id fallback. The description links usage and focus to visible outcomes (what the workspace is for, what the person wants to do first), but leaves idioma, nombre's 80-char constraint, and the workspace_id resolution rule entirely to the schema.

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?

The description names a specific verb and resource and enumerates the concrete effects: renames the workspace (conditioned on owner/admin), stores usage and focus, and writes a first note in today's Journal. That is far beyond restating the name. It does not explicitly contrast with the sibling update_workspace, which handles a subset of the same mutation, so an agent must infer the distinction from the welcome-flow framing.

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?

Explicitly states that the welcome card invokes it automatically and that the agent should call it directly only when the client does not render cards and the person replied in writing. That is a clear when-to-use plus a when-not-to-use condition, which is exactly what an agent needs to avoid double-invocation.

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