Skip to main content
Glama

Por categoria

painel_get_category_breakdown
Read-onlyIdempotent

Comissão e vendas (BRL) por CATEGORIA de produto no período, de todos os marketplaces que informam categoria (as demais vão para "Outros").

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_category_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

A3.8/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 new behavioral context: the data spans 'all marketplaces that report category' and non-reporting ones are folded into an 'Outros' bucket, which is exactly the kind of data-quality caveat an agent would otherwise misinterpret as missing data.

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 sentence that front-loads the metric and dimension, with the 'Outros' caveat appended where it belongs. No filler, no restatement of the title.

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 does the necessary work of saying what comes back (commission and sales in BRL per category) and what dimension the rows are keyed on. It omits only minor details such as the default 30-day window, which the schema already supplies.

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 fully documented in the schema, establishing the baseline of 3. The description adds nothing about period semantics or the interaction between days and start/end, so it does not exceed that baseline.

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 specific metric (commission and sales in BRL) and a specific grouping dimension (product category) over a period, which distinguishes it from dimension-based siblings like channel or advertiser breakdowns. It does not name any sibling explicitly, so differentiation rests on the dimension label alone.

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 category dimension implies when to reach for this tool versus painel_get_channel_breakdown or painel_get_products_by_period, but the description never states an explicit when-to-use or when-not condition, nor does it route the agent to an alternative.

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