Skip to main content
Glama
Expert-Integrado

Conexa MCP

by Expert-Integrado
OverviewSchemaRelated ServersScoreDiscussions
TypeScript
Remote

POST /recurringSale (Recurring Sale)

create_recurring_sale

Create a recurring sale for a product or hourly package. Specify customer, type, reference, frequency, occurrence count, start date, and amount.

Instructions

Criação de uma Venda Recorrente , cujo produto pode ser Serviço/Item ou Pacote de Horas (apenas Conexa Coworking) no sistema Conexa. ⚠ Fique atento ao produto do seu sistema. Há campos que não são necessários!

Campos do body:

  • customerId (integer) [obrigatório]: ID do cliente

  • type (string) [obrigatório]: 'product' para venda de Serviço/Item. 'package' para venda de Pacotes de Horas.

  • referenceId (integer) [obrigatório]: ID do Serviço/Item ou do Pacote de Horas

  • requesterId (integer): ID do solicitante

  • sellerId (integer): ID do vendedor (usuário)

  • frequency (string) [obrigatório]: Frequência da Venda Recorrente, podendo ser: 'daily' , 'weekly' , 'monthly' , 'bimonthly' , 'quarterly' , 'semester' , 'yearly'

  • isRepeat (boolean): Repetir a venda conforme a periodicidade ( frequency )

  • occurrenceQuantity (integer) [obrigatório]: Quantidade de ocorrências

  • startDate (string) [obrigatório]: Data de início

  • lastAdjustmentDate (string): Data do último reajuste

  • quantity (integer): Quantidade (não disponível para o tipo 'package' )

  • amount (decimal) [obrigatório]: Valor da venda recorrente

  • notes (string): Observações

  • isDiscountPreviousReservations (boolean): Aplicar desconto do Pacote de Horas em reservas anteriores

  • isCalculateProRata (boolean): Calcular Pro Rata proporcional ao mês de início da venda recorrente

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
bodyYesCorpo JSON da requisição (campos na descrição da tool)

Tool Definition Quality

B3.1/5.0
Behavior2/5

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

Annotations already indicate it's not read-only and not destructive. The description adds minimal behavioral context beyond the creation purpose. It warns about unnecessary fields but does not disclose side effects, idempotency, or authorization requirements.

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 well-structured with a clear purpose statement, a warning, and a bulleted list of fields. It is front-loaded but could be slightly more concise without losing essential information.

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?

For a tool with no output schema, the description adequately explains input parameters. However, it lacks context about return values, error handling, and how this tool relates to siblings like 'create_sale' or 'create_charge'.

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?

The description lists all fields in the body with types, required status, and brief explanations (e.g., 'customerId: ID do cliente'). Since the input schema does not define these properties, the description carries the full burden and provides meaningful semantics for each parameter.

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 the tool creates a recurring sale ('Criação de uma Venda Recorrente') and specifies the product types (Service/Item or Package of Hours). It distinguishes from similar tools like 'create_sale' by the recurring nature, though it does not explicitly contrast them.

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

Usage Guidelines2/5

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

No explicit guidance on when to use this tool versus alternatives like 'create_sale' or other creation tools. The description warns about unnecessary fields but does not provide context for selecting this tool over siblings.

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