Skip to main content
Glama

Diretos vs indiretos (por marketplace)

painel_get_direct_indirect
Read-onlyIdempotent

Vendas DIRETAS (produto/loja do próprio link) vs INDIRETAS (outro produto/loja comprado após o clique), quebradas por marketplace em byMarketplace[]. Fontes: Amazon (relatório de Categorias, em ITENS; sem comissão separada), Shopee ("Tipo de atribuição": mesma loja vs loja diferente, em produtos, COM comissão separada — directCommissionBrl/indirectCommissionBrl) e Mercado Livre (quantity_direct/quantity_not_direct, em pedidos). Cada item traz direct, indirect e directShare (0–1).

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "painel_get_direct_indirect"
  }
}

Input Schema

NameRequiredDescriptionDefault
daysNoAlternativa a start/end: janela de N dias terminando em end_date (default 30).
end_dateNoFim do período (yyyy-mm-dd). Opcional (default: hoje).
start_dateNoInício do período (yyyy-mm-dd). Opcional — ex.: "2026-06-01".

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive, and the description goes well beyond them: it discloses data provenance, that denominations differ per source (ITENS vs produtos vs pedidos), that Amazon has no separate commission while Shopee does, and the exact commission field names. It does not cover what happens for marketplaces without data, which keeps it from 5.

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?

Front-loads the direct-vs-indirect definition, then the per-marketplace breakdown, then the field contract. Dense but every clause carries information; the source-by-source enumeration is slightly heavy but justified given inconsistent units across marketplaces.

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?

With no output schema, the description usefully specifies the return shape (`byMarketplace[]` items containing direct, indirect, directShare 0–1) and unit caveats per source, which is exactly what an agent needs to interpret results. Missing only behavior for empty/unsupported marketplaces.

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 description coverage is 100%, so days/start_date/end_date are already fully documented, including the start/end vs days alternative. The description adds nothing about parameter behavior (e.g., precedence of days over start/end, timezone of 'today'), so baseline 3 applies.

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?

States a concrete analytical resource: direct vs indirect sales split by marketplace, returned in `byMarketplace[]`. The scope is precise and the per-source semantics (Amazon/Shopee/Mercado Livre) make the purpose unambiguous. It stops short of naming a sibling it must not be confused with, so it stops at 4.

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 description makes the analytical use case implied (attribution analysis of direct vs indirect sales per marketplace), but never states when to pick this over painel_compare_marketplaces or painel_get_channel_breakdown. No exclusions or prerequisites are given.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources