Conexa MCP

GET /recurringSale/:id (Recurring Sale)

get_recurring_sale

Read-only

Retrieve recurring sale details by providing the sale ID.

Instructions

Recuperação das informações de uma Venda Recorrente, a partir do ID, no sistema Conexa. ⚠ Fique atento ao produto do seu sistema. Há campos que não serão retornados!

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": {
      "id": "<id>"
    },
    "name": "get_recurring_sale"
  }
}

Input Schema

Name	Required	Description	Default
`id`	Yes	Valor de :id na rota /recurringSale/:id

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Jul 10, 2026

TDQS

A4/5.0

Behavior4/5

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

Annotations already indicate readOnlyHint=true, openWorldHint=true, and destructiveHint=false, which the description does not contradict. The description adds valuable context: a warning that some fields may not be returned depending on the product/system. This goes beyond the annotations by alerting the agent to variability in output.

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

Conciseness5/5

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

The description is concise: two sentences that front-load the purpose and provide a critical warning. Every word serves a purpose. No redundancy or extraneous information.

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?

For a simple retrieval with one parameter, no output schema, and strong annotations (readOnlyHint, openWorldHint), the description is complete. It explains what the tool does, the required input, and a caveat about variable output. Not detailing the response structure is acceptable given the openWorldHint and the warning.

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?

Schema coverage is 100% and the parameter description ('Valor de :id na rota /recurringSale/:id') essentially restates the route parameter. The description adds no additional meaning beyond the schema, so the baseline of 3 applies.

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 the action ('Recuperação das informações' / retrieve information), the resource ('Venda Recorrente' / recurring sale), and the identifier ('a partir do ID' / by ID). This is specific and distinct from sibling tools like list_recurring_sales.

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?

No explicit when-to-use or when-not-to-use guidance is provided. Usage is implied for retrieving a single recurring sale by ID, but alternatives like list_recurring_sales are not mentioned. Given the tool's simplicity, the lack of explicit guidance is acceptable but not ideal.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server