Skip to main content
Glama

Pedidos por status

painel_get_status_breakdown
Read-onlyIdempotent

Pedidos do período agrupados por status normalizado: pending (a receber), confirmed (concluídos), unpaid ("não pago" da Shopee — aguardando pagamento, FORA dos totais, como no relatório da Shopee) e cancelled (cancelados), com itens, comissão e GMV de cada grupo.

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_status_breakdown"
  }
}

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

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, closed-world, so safety is covered. The description adds genuinely valuable behavior beyond that: the normalization scheme and the critical caveat that unpaid orders sit FORA dos totais (excluded from totals), matching Shopee's own reporting, which prevents an agent from summing the groups and getting a wrong total.

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?

A single front-loaded sentence: the aggregation comes first, then the bucket definitions, then the per-group metrics. Every clause earns its place — the parentheticals are the semantics, not padding.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

No output schema exists, and the description compensates by naming the per-group contents (items, commission, GMV). Combined with annotations covering the safety profile and the schema covering the period parameters, an agent has everything needed to call it and interpret the result correctly.

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 all three parameters (days, start_date, end_date) and their defaults are already fully documented in the schema. The description adds nothing parameter-specific beyond 'do período' and doesn't clarify how days and start/end interact, so the baseline 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?

States a specific verb+resource (orders in the period grouped by normalized status) and enumerates the exact buckets with their meanings in parentheses. This makes it immediately distinguishable from siblings like painel_get_cancellations or painel_get_sales_summary, which also aggregate orders but not by normalized status.

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?

Usage is implied by the aggregation described — an agent can infer this is the tool for a status-level breakdown of orders. However, no sibling is named as an alternative or exclusion (e.g., painel_get_cancellations already covers cancelled orders, and painel_get_sales_summary covers total GMV), so the agent must reason about the overlap itself.

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