Skip to main content
Glama
Sign In
hotmart-mcp

hotmart-mcp

by thaleslaray
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

hotmart_negotiation_preview_app

Preview negotiation proposals for delinquent subscriptions by simulating installment plans or discounts. Confirm to generate the negotiation.

Instructions

Preview de proposta de negociação antes de gerar.

Mostra os parâmetros e dispara o hotmart_negotiation_generate se confirmado. Use pra 'simular negociação pro assinante X', 'preview parcelamento'. NÃO gera por padrão — só prévia visual.

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": {
      "subscription_id": "<subscription_id>"
    },
    "name": "hotmart_negotiation_preview_app"
  }
}

Input Schema

NameRequiredDescriptionDefault
subscription_idYesID/code da assinatura inadimplente.
payment_typeNoBILLET | PIX | CREDIT_CARD. **Note: API uses English 'BILLET' (NOT 'BOLETO')**.BILLET
recurrencesNoNúmero de parcelas (1 = à vista).
discountNoDesconto como **fração 0-1** (ex: 0.25 = 25% off). NOT percent.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.3.3

TDQS

A3.9/5.0
Behavior3/5

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

The description states it shows parameters and triggers generate if confirmed, and explicitly says it does not generate by default. With no annotations, it partially compensates but does not disclose what happens after confirmation or any side effects.

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 concise (4 sentences) and front-loaded with the core purpose. It efficiently conveys the tool's primary function and relationship to generate, with minimal waste.

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 4 parameters, no output schema, and no annotations, the description covers the tool's function and usage context well. It could be improved by hinting at what the preview outputs (e.g., calculated values) but is sufficient for an agent.

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?

Input schema has 100% coverage with parameter descriptions. The description does not add new meaning beyond schema; it only reinforces the preview purpose. Baseline 3 is appropriate.

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 it is a 'Preview de proposta de negociação' before generating, and identifies the specific resource (negotiation proposal). It distinguishes itself from the sibling tool hotmart_negotiation_generate by noting it triggers generate only upon confirmation.

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?

Provides explicit usage contexts like 'simular negociação pro assinante X' and 'preview parcelamento', and clarifies it does not generate by default. However, it does not mention when not to use it or provide alternative tools.

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