Skip to main content
Glama

get_task_destinations

Read-onlyIdempotent

Dónde puede nacer una tarea además de Secondbrain: las listas de ClickUp y los proyectos de Jira que el workspace tiene conectados y activados.

Usar ANTES de create_task / update_task cuando la persona pide una tarea "en
Jira" o "en ClickUp" (o "en la lista UBI", "en el proyecto SB") y no se sabe
cómo se llama el destino. De cada uno: `id`, nombre, `clave` (Jira),
dónde está, si `sube` (false = modo «Traer»: baja de allá pero no recibe
tareas nuevas) y si es el `por_defecto` (donde caen las tareas nuevas que no
eligen otro destino, y lo hacen solas).

Si un workspace no devuelve nada de una herramienta, no la tiene conectada:
se conecta desde la app (how_to_in_app).

Sin workspace_id mira todos a la vez.

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

Input Schema

NameRequiredDescriptionDefault
workspace_idNoUUID del workspace, o su nombre tal como lo dice el usuario ('Acme', 'el personal'). Omitir = TODOS los workspaces de la persona, en una sola llamada

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive, and the description goes beyond them by explaining the returned field semantics (`sube` false = 'Traer' mode, `por_defecto` = where unassigned new tasks land) and, crucially, what an empty result means: the tool isn't connected and must be enabled from the app via how_to_in_app. That empty-result rule is the kind of operational context annotations cannot convey.

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?

Purpose is front-loaded, then usage, then return fields, then edge case — a sensible order. The middle sentence enumerating return fields runs long and mixes '-' style fragments, but no sentence is filler.

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?

With no output schema, the description compensates by enumerating the returned fields and their meaning, plus the empty-result and default-destination behaviour. Nothing an agent needs to call this correctly and interpret the result is missing, even for a non-Spanish reader who must map the field names.

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 there is only one optional parameter whose format (UUID or user-spoken name) is fully documented in the schema. The description's 'Sin workspace_id mira todos a la vez' restates the schema's omit semantics, so baseline 3 applies.

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?

Names the exact resource set — ClickUp lists and Jira projects connected to the workspace — and frames it as the universe of task origins besides Secondbrain. An agent can tell this apart from get_boards or get_task_detail without opening the schema.

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 says to call it BEFORE create_task/update_task when the user names a destination ('en Jira', 'en ClickUp', 'la lista UBI') and the destination identifier is unknown. It also states the no-workspace_id case ('mira todos a la vez'), so both branches are covered.

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