Ekyte MCP Server

Listar Usuários do Ekyte

ekyte_list_users

Read-onlyIdempotent

List company members from Ekyte with search by name or email. Returns user ID, name, and email for easy identification.

Instructions

Lista usuários/membros da empresa no Ekyte.

👉 PREFIRA usar "search" (busca por nome OU email, case-insensitive) para achar alguém rapidamente. Ex: search="pietro".

Retorna: id (UUID), nome, email.

IMPORTANTE: O ID do usuário é um UUID (ex: "feff4a61-b0a3-483d-a384-172c4b301ee0"), não um número.

Paginação client-side: 50 por página.

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

Input Schema

Name	Required	Description	Default
`search`	No	Filtro de texto (case-insensitive) por nome ou email.
`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.5/5.0

Behavior4/5

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

Annotations already declare the tool as read-only and idempotent. The description adds behavioral details: IDs are UUIDs, pagination is client-side (50 per page), and search is case-insensitive. This enriches the agent's understanding of behavior beyond 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?

The description is very concise (three short sentences) with front-loaded purpose and key usage tips. Every sentence adds value: purpose, search preference, return fields, UUID warning, and pagination. No unnecessary words.

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?

Without an output schema, the description fully specifies the return fields (id, name, email) and pagination behavior. It covers all three optional parameters with usage guidance. The tool has moderate complexity, and the description leaves no gaps for an agent to understand its usage.

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 baseline is 3. The description adds significant context: search is case-insensitive with an example, page indicates client-side pagination with 50 per page, and response_format is described. This goes beyond the schema's bare 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 'Lista usuários/membros da empresa no Ekyte', specifying the action (list) and resource (users). It is distinct from sibling tools, which focus on tasks, projects, and time entries.

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?

The description recommends preferring the 'search' parameter for quick lookups, providing explicit usage guidance. However, it does not explicitly mention when not to use this tool or compare with alternatives, though no alternative exists for listing users.

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