Skip to main content
Glama
raylann-lopes

MCP Movidesk Server

criar_ticket

Create a new Movidesk support ticket with formatted macro and escalation options. Use after support to register the service; requires client email or ID from a prior customer lookup.

Instructions

Cria um novo ticket no Movidesk com macro de suporte formatada em HTML. Ideal para registrar atendimentos após o suporte. Suporta macros de atendimento e escalonamento. SEMPRE use a ferramenta 'consultar_cliente' ANTES para pegar o email ou id do cliente (você NÃO PODE tentar adivinhar ou embutir um CPF/CNPJ ou Nome, a api apenas suportará dados reais vindos da consulta do cliente no movidesk)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
tagsNoTags/etiquetas para categorizar o ticket (lista de strings)
assuntoYesTítulo/assunto do ticket (mínimo 3 caracteres)
urgenciaNoNível de urgência do ticket: Baixa, Média, Alta ou UrgenteBaixa
categoriaNoCategoria do ticket. Opções: 'Dúvida', 'Problema', 'Solicitação de serviço', 'Sugestão'
descricaoYesDescrição detalhada do problema ou solicitação. Pode usar Markdown para formatação (negrito, listas, etc.)
tipoMacroNoTipo de macro a aplicar: 'atendimento' (padrão), 'escalonamento' ou 'nenhuma'atendimento
observacoesNoObservações adicionais sobre o atendimento
tipoServicoNoTipo de serviço associado ao ticket (ex: 'Vendas', 'Suporte'). Use o nome exato cadastrado no Movidesk.
versaoBancoNoVersão do(s) banco(s) / sistema do cliente (ex: 2025.002)
emailClienteYesEmail, CPF, CNPJ ou ID do cliente que está cadastrado no Movidesk
nivelServicoNoSub-nível do serviço (ex: 'Nivel Basico', 'Nivel 1'). Usado junto com tipoServico.
equipeDestinoNo(Escalonamento) Equipe para a qual o ticket será escalonado
nomeAtendenteNoNome do atendente que realizou o suporte
responsavelIdNoID do agente responsável pelo ticket. Se não informado, usa o owner padrão da conta.
sistemaAfetadoNoSistema ou módulo que foi afetado pelo problema
solucaoAplicadaNoSolução que foi aplicada para resolver o problema (se resolvido)
canalAtendimentoNoCanal pelo qual o atendimento foi realizado
equipeResponsavelNoNome da equipe responsável pelo ticket (ex: 'Administradores', 'Atendimento').
motivoEscalonamentoNo(Escalonamento) Motivo pelo qual o ticket está sendo escalonado
tentativasResolucaoNo(Escalonamento) O que já foi tentado para resolver o problema
Behavior3/5

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

No annotations are provided, so the description carries the burden. It discloses key behaviors: the ticket is created with a support macro formatted in HTML, supports macros 'atendimento' and 'escalonamento', and that client data MUST come from a real query. However, it does not mention side effects, error handling, or response formats, which are relevant for a mutation tool.

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 concise: three sentences, front-loaded with the main action. Each sentence provides valuable information—purpose, use case, and a critical prerequisite—without superfluous detail.

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 the tool's complexity (20 parameters, no output schema), the description is complete enough by covering the tool's purpose, usage context, macro types, and the mandatory prerequisite of using consultar_cliente. The schema handles parameter details, so the description does not need to enumerate all optional fields.

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% (0.0), so the baseline is 3. The description adds meaning beyond the schema by emphasizing that emailCliente must be obtained from 'consultar_cliente' and cannot be guessed, and by explaining the purpose of macro types ('atendimento' and 'escalonamento'). This raises the score.

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 'Cria um novo ticket no Movidesk' (Creates a new ticket in Movidesk) with a specific verb and resource. It also distinguishes from sibling tools by indicating that it creates tickets and supports macros, while sibling tools are for viewing, searching, or modifying tickets.

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 provides clear context: 'Ideal para registrar atendimentos após o suporte' (ideal for recording after support) and explicitly instructs to use 'consultar_cliente' BEFORE to retrieve client data, which is a strong usage guideline. It does not explicitly mention alternatives or exclusions, but the context is sufficient to know when to use it.

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/raylann-lopes/mcp_eagle'

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