Skip to main content
Glama
Sign In
MCP Movidesk Server

MCP Movidesk Server

by raylann-lopes
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

alterar_status_ticket

Update a Movidesk ticket's status to Novo, Em atendimento, Parado, Resolvido, Cancelado, or Fechado. Provide a justification when required, such as for Parado or Cancelado.

Instructions

Altera o status de um ticket no Movidesk. Status disponíveis: 'Novo', 'Em atendimento', 'Parado', 'Resolvido', 'Cancelado', 'Fechado'. Alguns status como 'Parado' e 'Cancelado' exigem justificativa obrigatória.

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": {
      "ticketId": "<ticketId>",
      "novoStatus": "<novoStatus>"
    },
    "name": "alterar_status_ticket"
  }
}

Input Schema

NameRequiredDescriptionDefault
ticketIdYesID numérico do ticket a ter o status alterado
novoStatusYesNovo status do ticket em português: 'Novo', 'Em atendimento', 'Parado', 'Resolvido', 'Cancelado' ou 'Fechado'
justificativaNoJustificativa para a mudança de status (obrigatória para alguns status como 'Parado' e 'Cancelado')

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A4/5.0
Behavior3/5

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

With no annotations, the description carries the full burden and does disclose that some statuses require a mandatory justification. It does not, however, cover other behavioral aspects such as permission requirements, reversibility, or possible side effects like notifications, leaving some transparency gaps.

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 compact, front-loaded with the action, and uses two sentences to convey the core purpose and the conditional requirement. Every clause earns its place without redundancy.

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 simplicity of the tool and fully described parameters, the description covers the main purpose and the one non-obvious constraint (justification for certain statuses). It lacks explicit guidance on error scenarios or post-conditions, but for a status mutation tool this is adequate.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The schema has 100% coverage with descriptions for all three parameters, so the baseline is 3. The description's mention of available statuses and justification requirement merely duplicates what is already in the property descriptions, adding no new semantic meaning.

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 verb 'Altera' and the resource 'status de um ticket no Movidesk', which precisely distinguishes it from sibling tools that create, consult, or list tickets. It also lists the allowed statuses, reinforcing the specific action.

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 that this tool is for changing ticket statuses and enumerates the allowed statuses. However, it does not explicitly mention when not to use it or compare it with alternatives like adicionar_interacao or atribuir_agente, so it stops short of full exclusion guidance.

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

Deploy Server

Other Tools