Skip to main content
Glama
Expert-Integrado

Conexa MCP

by Expert-Integrado
OverviewSchemaRelated ServersScoreDiscussions
TypeScript
Remote

PATCH /plan/:id (Plan)

update_plan

Update a plan in the Conexa contract registration system. Modify plan fields like name, payment options, product quotas, and service correspondence limits.

Instructions

Atualiza um plano, utilizado no cadastro de contrato, no sistema Conexa.

Campos do body:

  • companyId (integer): ID da unidade

  • name (string): Nome do plano ( deve ser único )

  • serviceCategoryId (integer): ID da categoria de serviço

  • costCenterId (integer): ID do centro custo

  • description (string): Descrição do plano

  • paymentPeriodicities (array of objects): Opções de periodicidade de pagamento

  • paymentPeriodicities[].periodicity (string) [obrigatório]: Periodicidade de pagamento, podendo ser: monthly , bimonthly , quarterly , semester ou yearly

  • paymentPeriodicities[].amount (decimal) [obrigatório]: Valor do plano para a periodicidade

  • membershipFee (decimal): Taxa de adesão

  • refundValue (decimal): Valor de depósito retornável

  • fidelityMonths (integer): Quantidade de meses de fidelidade

  • productQuotas (array of objects): Lista de cotas de serviços/itens (produtos) vinculadas ao plano

  • productQuotas[].productId (integer) [obrigatório]: ID do serviço/item

  • productQuotas[].quantity (integer) [obrigatório]: Quantidade de cotas

  • dueDay (integer): Dia do vencimento do plano "Cliente Avulso"

  • nfseDescription (string): Descrição da nota fiscal

  • receiptDescription (string): Descrição do recibo (depende de configuração)

  • discountOnRooms (decimal): Valor em percentual de desconto para reserva em salas

  • discountOnWorkstation (decimal): Valor em percentual de desconto para reserva em ambientes compartilhados

  • isSmsEnabled (boolean): Flag de envio de SMS

  • serviceCorrespondenceQuotas (object): Configura as cotas de atendimentos e correspondências (depende de configuração)

  • serviceCorrespondenceQuotas.limited (boolean): Define se a quantidade de atendimentos e correspondências é ou não limitada

  • serviceCorrespondenceQuotas.messagesLimit (integer) [obrigatório]: Define o limite de atendimentos e correspondências. Definir como 0 para não adicionar cotas ao contrato

  • serviceCorrespondenceQuotas.priceAdditionalMessage (decimal) [obrigatório]: Define o valor adicional por atendimentos e correspondências, caso seja ultrapassado

  • bookingModels (array of objects): Lista de modelos de reserva (Estações de Trabalho do Ambiente Compartilhado)

  • bookingModels[].id (integer) [obrigatório]: ID do modelo de reserva

  • bookingModels[].stations (integer) [obrigatório]: Quantidade de estações

  • privateSpaceIds (array): Lista de IDs de espaços privativos associados ao plano

  • hourQuotas (array of objects): Lista de cotas de horas para uso de salas ou ambientes compartilhados

  • hourQuotas[].hours (integer) [obrigatório]: Quantidade de horas inclusas

  • hourQuotas[].periodicity (string) [obrigatório]: Frequência de disponibilidade de cota, podendo ser: daily , weekly ou monthly

  • hourQuotas[].spaceId (integer) [obrigatório]: ID do espaço

  • hourQuotas[].groupId (integer) [obrigatório]: ID do grupo

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesValor de :id na rota /plan/:id
bodyYesCorpo JSON da requisição (campos na descrição da tool)

Tool Definition Quality

A3.8/5.0
Behavior3/5

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

Annotations already indicate readOnlyHint=false and destructiveHint=false, which are consistent with the update operation described. The description adds no additional behavioral context (e.g., permissions, side effects, partial update behavior). It merely restates the update action.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

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

The description starts with a clear one-line summary, then lists all body fields in an organized manner. While the list is long, it is necessary given the complexity of the plan object. The structure is logical, but could be slightly more concise by using a table or reference. However, it remains easily parseable.

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 high number of parameters and no output schema, the description does a good job covering the input fields, including required markers and allowed values. However, it lacks information about return values, error handling, or update semantics (e.g., whether omitted fields are preserved or reset). The annotations provide basic safety context but not full completeness.

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

Parameters5/5

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

The input schema only defines two parameters (id and body) with minimal descriptions. The tool description provides exhaustive detail for all body fields, including data types, required status (marked as [obrigatório]), and constraints (e.g., unique name, periodicity options). This adds significant meaning beyond the schema's simple description.

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 'Atualiza um plano' (Updates a plan), which is a specific verb+resource. It distinguishes from sibling tools like create_plan and delete_plan, but does not explicitly differentiate from other update tools like update_contract or update_product. The context 'utilizado no cadastro de contrato' adds usage context.

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

Usage Guidelines3/5

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

The description gives one usage context ('utilizado no cadastro de contrato') but does not specify when to use this tool vs alternatives (e.g., create_plan for new plans, delete_plan for removal). No explicit when-not-to-use or prerequisite information is provided.

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/Expert-Integrado/conexa-mcp'

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