Cria um produto na Cakto. A criação já gera automaticamente a oferta padrão e o checkout do produto (não existe endpoint separado de criar checkout). Requer o escopo "write products" no app do Painel Cakto.
| Name | Required | Description | Default |
|---|---|---|---|
| name | Yes | ||
| type | No | ||
| price | No | ||
| account | No | ||
| category | No | ||
| guarantee | No | ||
| sales_page | No | ||
| description | Yes |
Changes observed during successful MCP inspections.
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Beyond annotations, the description reveals key side effects: it auto-generates the default offer and checkout, and it requires the 'write products' scope. This adds meaningful behavioral context that annotations do not provide.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is short and front-loaded with the core action, followed by important side-effect and authorization details. Every sentence adds value with no redundancy.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
While it covers the main action, side effects, and auth, it leaves the meaning of several parameters undocumented and does not describe the return value. For a tool with eight parameters and no output schema, this is a significant gap.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 0%, and the description provides no explanation for the eight parameters. It does not compensate for the missing schema descriptions by clarifying fields like price, type, account, guarantee, or sales_page.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the action and resource: 'Cria um produto na Cakto.' It also distinguishes itself from sibling tools by explaining that creation automatically generates the default offer and checkout, making the purpose unambiguous.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
It explicitly notes that no separate checkout endpoint exists, guiding the agent to use this tool for checkout creation. It also implies that the default offer is handled here rather than via cakto_offers_create, though it does not name alternatives explicitly.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.