Skip to main content
Glama
Expert-Integrado

Conexa MCP

PATCH /contract/:id (Contract)

update_contract

Update contract details including dates, amounts, services, quotas, and custom fields in the Conexa system.

Instructions

Edição de um contrato no sistema Conexa.

Campos do body:

  • startDate (date): Data de início do contrato

  • dueDay (integer): Dia de vencimento (caso só exista um contrato ativo no cliente)

  • fidelityDate (date): Data de fidelidade

  • contractSummary (string): Descrição resumida do contrato

  • amount (decimal): Valor do contrato

  • discountValue (decimal): Desconto de contrato

  • notes (string): Observações

  • lastAdjustmentDate (date): Último reajuste do contrato

  • sellerId (integer): ID do vendedor (usuário). Deve ser enviado em requisições que a autenticação é realizada pelo API Token

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

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

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

  • complementaryServices (array of objects): Define os serviços complementares que serão adicionados ao contrato

  • complementaryServices[].productOrServiceId (integer): Id do produto ou serviço

  • complementaryServices[].quantity (integer): Quantidade do produto ou serviço

  • complementaryServices[].amount (decimal): Valor final do serviço

  • complementaryServices[].notes (string): Observações

  • extraFields (array of objects / null): Lista de campos extras do contrato. Enviar null ou omitir para não alterar. Enviar [] para remover todos. Os campos extras devem ser do tipo contract

  • extraFields[].id (integer): ID do campo extra

  • extraFields[].value (string): Valor do campo extra

  • plan (object): Plano (apenas para planos personalizados)

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

  • plan.costCenterId (integer): ID do centro de custo

  • plan.nfseDescription (string): Descrição do serviço na NFS-e

  • discountOnRooms (decimal): Descontos em salas

  • discountOnWorkstation (decimal): Descontos em ambientes compartilhados

  • privateSpaceId (integer): ID de um espaço privativo que será vinculado ao contrato

  • isSmsEnabled (boolean): Habilitar envios de atendimento e correspondência por SMS

  • serviceCorrespondenceQuotas (object): Cotas de atendimento e correspondência

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

  • serviceCorrespondenceQuotas.messagesLimit (integer): Define o limite de atendimentos ou correspondências. Definir como 0 para não adicionar cotas ao contrato

  • serviceCorrespondenceQuotas.priceAdditionalMessage (decimal): Define o valor a ser pago por atendimentos ou correspondências caso o limite seja ultrapassado

Input Schema

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

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

Annotations already indicate non-read-only and non-destructive. The description adds the note that sellerId must be used with API Token authentication, and lists fields, but does not clarify update semantics (partial vs full replace, behavior of omitted fields). More context on how the update works would improve transparency.

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

Conciseness3/5

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

The description is lengthy due to the many fields, but it is structured with a header and list. However, it could be more concise by reducing redundancy or grouping related fields. The key action is front-loaded in the first line, but the large block of text may overwhelm agents.

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?

The description fully covers the input parameters, which is the main complexity. However, it lacks information about the return value (likely the updated contract) and possible error conditions. This gap reduces completeness, especially given no output schema.

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 provides only id and body as parameters, with body simply described as 'Corpo JSON'. The description extensively documents all allowed body fields with types and meanings, thus adding essential semantics beyond the schema. This is critical for correct tool invocation.

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 'Edição de um contrato' (editing a contract) and the tool name 'update_contract' and title 'PATCH /contract/:id (Contract)' unambiguously indicate the action and resource. It is easily distinguished from siblings like create_contract, delete_contract, and end_contract.

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 purpose is implied by the name and description ('Edição de um contrato'), but there is no explicit guidance on when to use this tool vs alternatives (e.g., create_contract for new contracts, delete_contract for removal). No when-not or context 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