Ekyte MCP Server

Criar Projeto no Ekyte

ekyte_create_project

Creates a project in Ekyte by providing required name and workspace, with optional template, dates, and additional payload for custom fields.

Instructions

Cria um novo projeto no Ekyte baseado nos parâmetros e num payload adicional dinâmico.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "name": "<name>",
      "workspaceId": "<workspaceId>"
    },
    "name": "ekyte_create_project"
  }
}

Input Schema

Name	Required	Description
`name`	Yes	Nome do projeto
`workspaceId`	Yes	ID do workspace onde o projeto será criado
`templateId`	No	ID do modelo (template) do projeto, se houver
`startDate`	No	Data de início no formato YYYY-MM-DD
`endDate`	No	Data final no formato YYYY-MM-DD
`endpoint_override`	No	Opcional: override da rota de criação. Padrão é 'projects'.
`additional_payload`	No	Campos adicionais que podem ser requeridos pelo Ekyte para criar um projeto (JSON)

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Jun 4, 2026

TDQS

A3.6/5.0

Behavior4/5

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

Annotations indicate a non-read-only, non-destructive, non-idempotent write operation. The description adds context about a dynamic additional payload, which aids understanding of the tool's behavior. No contradictions 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.

Conciseness5/5

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

A single, clear sentence that efficiently conveys the tool's purpose. It is front-loaded with the action and avoids unnecessary words, earning its place with no redundancy.

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?

Given the lack of an output schema, the description should ideally mention return values. It also omits details about error handling, authentication requirements, or the behavior of endpoint_override. While concise, it leaves gaps for a complex tool with 7 parameters and a dynamic payload.

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%, so parameters are already well-documented. The description adds value by emphasizing the dynamic nature of additional_payload and hinting that extra fields may be required by Ekyte, going beyond the schema's static descriptions.

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 clearly states 'Cria um novo projeto' (creates a new project), specifying the verb and resource. However, it does not explicitly distinguish from sibling tools like ekyte_create_task, relying on the tool name for differentiation.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

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

No guidance is provided on when to use this tool versus alternatives (e.g., ekyte_create_task for tasks). The description lacks contextual recommendations or exclusions, making it less helpful for an AI agent deciding which tool to invoke.

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