Skip to main content
Glama
FerrazPiai

Ekyte MCP Server

by FerrazPiai

Criar Tarefa no Ekyte (fase única ou multi-fase)

ekyte_create_task
Destructive

Create tasks in Ekyte with single or multi-phase assignments, assigning different executors per phase. Specify title, workspace, task type, dates, and optionally priority and description.

Instructions

Cria uma nova tarefa no Ekyte. Suporta DOIS modos:

MODO 1 — FASE ÚNICA (simples): Forneça executor_id + phase_id. Tarefa nasce com 1 fase.

MODO 2 — MULTI-FASE (com executores diferentes por fase): Forneça phases[] com uma entrada por fase. Cada entrada tem { phase_id, executor_id, effort_minutes, phase_start_date?, phase_due_date? }. A tarefa começa na PRIMEIRA fase da lista.

Fluxo recomendado ANTES:

  1. ekyte_list_workspaces → workspace_id

  2. ekyte_list_task_types → task_type_id (+ workflow_id)

  3. ekyte_list_phases(workflow_id) → phase_ids disponíveis

  4. ekyte_list_users → executor_id (UUID)

  5. Chamar este tool

IMPORTANTE: Sempre confirme TODOS os dados com o usuário antes de criar.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
titleYesTítulo da nova tarefa
workspace_idYesID numérico do workspace no Ekyte. Use ekyte_list_workspaces para descobrir o ID.
task_type_idYesID do tipo de tarefa. Use ekyte_list_task_types para descobrir o ID.
executor_idNoUUID do responsável principal. Obrigatório se phases[] NÃO for fornecido. Se phases[] for fornecido, é ignorado.
phase_idNoID da etapa/fase inicial. Obrigatório se phases[] NÃO for fornecido. Se phases[] for fornecido, é ignorado.
estimated_time_minutesNoTempo estimado total em minutos (ex: 60 para 1 hora). Ignorado em multi-fase: soma dos esforços de phases[].
phase_start_dateYesData de início padrão (AAAA-MM-DD). Cada fase pode sobrescrever em phases[].
phase_due_dateYesData de entrega padrão (AAAA-MM-DD). Cada fase pode sobrescrever em phases[].
descriptionNoDescrição detalhada da tarefa (opcional)
priorityNoPrioridade (0-1000). Ex: 100=Baixa, 300=Média, 500=Alta. Opcional.
phasesNoMULTI-FASE: lista de fases com executores distintos. Quando fornecido, executor_id/phase_id de cima são IGNORADOS — a tarefa começa na primeira fase da lista. Use para criar tarefas com pessoas diferentes em cada etapa do fluxo.
Behavior3/5

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

Annotations already indicate destructiveHint=true (creating a task) and readOnlyHint=false. The description adds context on mode usage and prerequisites, but does not disclose other behaviors like auth requirements or rate limits. No contradiction with annotations.

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 description is well-structured with clear sections (modes, recommended flow, important note) and is appropriately sized for the tool's complexity. Minor verbosity could be trimmed.

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?

Given the 11 parameters, two operating modes, and required prerequisite data, the description comprehensively covers usage context, mode selection, and pre-conditions. No output schema, but the description adequately sets expectations.

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 description coverage is 100%, but the description adds value by explaining inter-parameter dependencies (e.g., ignoring executor_id when phases[] is provided) and mode-specific parameter usage beyond individual schema descriptions.

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 clearly states it creates a new task in Ekyte, supporting two distinct modes (single phase and multi-phase). It uses a specific verb ('cria') and resource ('tarefa'), and differentiates from sibling tools like ekyte_update_task by detailing mode-specific behavior.

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?

Provides a recommended 5-step flow before calling and an important note to confirm with user. It distinguishes between single and multi-phase modes, but does not explicitly state when not to use this tool.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/FerrazPiai/ekyte_mcp_server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server