Skip to main content
Glama
FerrazPiai

Ekyte MCP Server

by FerrazPiai
OverviewSchemaRelated ServersScoreDiscussions
TypeScript
Hybrid

Editar Tarefa no Ekyte (fase atual / top-level)

ekyte_update_task
DestructiveIdempotent

Update an existing task's top-level fields (title, description, active phase, executor, dates, priority) using JSON Patch. Always confirm changes with user.

Instructions

Atualiza campos TOP-LEVEL de uma tarefa existente (título, descrição, executor/fase ATIVA, datas da fase atual, prioridade) usando JSON Patch.

Para editar executor/datas/esforço de uma FASE ESPECÍFICA não-atual, use ekyte_update_phase em vez deste.

Campos opcionais (pelo menos 1 obrigatório):

  • title: Novo título

  • description: Nova descrição (texto simples → convertido para HTML)

  • executor_id: UUID do novo responsável da fase atual

  • phase_id: ID da nova fase ATIVA (muda a fase corrente)

  • phase_start_date / phase_due_date: Datas da fase atual

  • priority_group: Grupo de prioridade (35=Baixa, 50=Média, 60=Alta, 90=Urgente)

  • priority: Prioridade bruta (0-1000) — normalmente prefira priority_group

IMPORTANTE: Sempre confirme as alterações com o usuário antes de executar.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
task_idYesID numérico da task no Ekyte. Use ekyte_list_tasks para descobrir o ID.
project_idNoID do projeto (necessário APENAS se for uma tarefa de projeto). Tarefas avulsas não precisam disso.
titleNoNovo título da tarefa (opcional)
descriptionNoNova descrição da tarefa em texto simples (será convertido para HTML). Opcional.
executor_idNoUUID do novo responsável da FASE ATUAL (opcional). Para trocar executor de uma fase específica não-atual, use ekyte_update_phase. Use ekyte_list_users para descobrir.
phase_idNoID da nova fase ATIVA da tarefa (opcional). Use ekyte_list_task_flow_phases para ver as fases disponíveis.
phase_start_dateNoNova data de início da etapa atual (AAAA-MM-DD). Opcional.
phase_due_dateNoNova data de entrega da etapa atual (AAAA-MM-DD). Opcional.
priority_groupNoGrupo de prioridade (0-100). É o campo que a UI do Ekyte usa: 35=Baixa, 50=Média, 60=Alta, 90=Urgente. Opcional.
priorityNoPrioridade numérica bruta (0-1000). Normalmente você quer priority_group em vez disso. Opcional.

Tool Definition Quality

A4.7/5.0
Behavior5/5

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

Beyond annotations (destructiveHint=true, idempotentHint=true), the description adds that the tool uses JSON Patch, converts description to HTML, and emphasizes user confirmation. 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?

Well-structured: purpose first, then parameter list, then important note. Efficiently covers all necessary information for 10 parameters without redundancy. Slightly longer due to parameter explanations, but each sentence earns its place.

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?

Given 10 parameters and no output schema, the description covers behavior, parameter details, usage guidelines, and a confirmation requirement. Complete enough for an agent to use correctly. Lacks return value description, but utility is clear.

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% (baseline 3), but description adds value: maps priority_group to labels (35=Baixa, etc.), advises preference for priority_group over priority, and explains description conversion. Adds meaning beyond schema.

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 the tool updates top-level fields of an existing task (title, description, executor, dates, priority). It distinguishes from the sibling tool ekyte_update_phase for editing specific phases, making the purpose unambiguous.

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 provides when-to-use vs alternatives: 'Para editar executor/datas/esforço de uma FASE ESPECÍFICA não-atual, use ekyte_update_phase em vez deste.' Also instructs to confirm changes with the user before executing.

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