Skip to main content
Glama
Expert-Integrado

Conexa MCP

POST /plan (Plan)

create_plan

Create a plan for contract registration by specifying name, payment options, product quotas, and discounts in the Conexa system.

Instructions

Criação de um plano, utilizado no cadastro de contrato, no sistema Conexa.

Campos do body:

  • companyId (integer) [obrigatório]: ID da unidade

  • name (string) [obrigatório]: Nome do plano ( deve ser único )

  • serviceCategoryId (integer) [obrigatório]: ID da categoria de serviço

  • costCenterId (integer) [obrigatório]: 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 em determinada periodicidade

  • membershipFee (decimal): Taxa de adesão

  • refundValue (decimal): Valor de deposito retornavel

  • fidelityMonths (integer): Meses de fidelidade

  • productQuotas (array of objects): Cotas de serviços/itens (produtos) que vão estar associadas ao plano

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

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

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

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

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

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

  • isSmsEnabled (boolean): Flag para verificar se envia SMS. Padrão: false

  • 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 a ser pago caso o limite de atendimentos e correspondências 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): IDs de espaços privativos que o plano contempla

  • hourQuotas (array of objects): Pacotes de horas

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

  • 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
bodyYesCorpo JSON da requisição (campos na descrição da tool)
Behavior4/5

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

Annotations are minimal (readOnlyHint false, destructiveHint false). The description adds behavioral context by stating constraints (e.g., name must be unique) and listing required fields. However, it does not detail side effects or success/error outcomes beyond creation.

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 is long due to many parameters, but it is well-structured front-loaded with purpose followed by field list. Each field earns its place; no redundancy. However, could use bullet points for readability.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Input is fully detailed, but there is no output schema or description of return values, error messages, or post-creation behavior. For a complex creation tool, this information would complete the context.

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 has only a generic body property, so the description provides all parameter details: types, required status, nested arrays, and examples. Schema coverage is 100%, and the description fully compensates with clear, structured field explanations.

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 starts with 'Criação de um plano' clearly stating the verb (creation) and resource (plan), and specifies its context 'utilizado no cadastro de contrato', distinguishing it from sibling tools like update_plan or delete_plan.

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 mentions usage in contract registration, but does not provide explicit when-to-use or when-not-to-use guidance, nor does it reference alternatives among siblings. More directive wording would improve.

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