Ekyte MCP Server

Listar Workspaces do Ekyte

ekyte_list_workspaces

Read-onlyIdempotent

List workspaces from Ekyte with optional search and status filter. Use to find clients or projects before creating tasks or logging time.

Instructions

Lista workspaces (clientes/projetos) da empresa no Ekyte.

👉 PREFIRA usar o parâmetro "search" para achar um workspace pelo nome (ex: search="ferraz" acha "V4 Ferraz Piai"). É mais rápido que iterar páginas.

Use esta ferramenta ANTES de criar tasks ou apontar horas. Retorna: id, nome, status (ativo/inativo).

Paginação client-side: 50 registros por página. Total típico: 600+ workspaces.

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

Input Schema

Name	Required	Description	Default
`search`	No	Filtro de texto (case-insensitive) no nome do workspace. Ex: 'ferraz' acha 'V4 Ferraz Piai'.
`active_only`	No	Se true, retorna só workspaces ativos (active=1).
`page`	No	Página do resultado filtrado (paginação client-side, 50 por página).
`response_format`	No	Formato de saída	markdown

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Jun 4, 2026

TDQS

A4.4/5.0

Behavior4/5

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

Annotations already declare readOnlyHint and idempotentHint. Description adds valuable behavioral context: client-side pagination (50 per page), typical total (600+), and search behavior. 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.

Conciseness5/5

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

Very concise, uses bullet points and emoji for readability. Front-loads purpose and usage tips, every sentence adds value. No wasted words.

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 purpose, usage scenario, search optimization, pagination details, and return fields. No output schema but mentions what returns. Completeness is adequate for a read-only list tool.

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 covers all parameters (100% coverage). Description enhances semantics with search example, case-insensitivity note, and pagination context beyond schema. Adds meaning beyond structured data.

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?

Description clearly states it lists workspaces (clientes/projetos) and specifies return fields (id, nome, status). It also distinguishes from sibling list tools by focusing on workspaces.

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?

Explicitly advises to prefer using the search parameter for efficiency and recommends using this tool before creating tasks or logging hours. Lacks explicit when-not-to-use but provides strong when-to-use guidance.

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