Skip to main content
Glama

Comparar marketplaces

painel_compare_marketplaces
Read-onlyIdempotent

Compara os marketplaces lado a lado no período (cliques, pedidos, comissão, GMV, EPC, conversão, ticket médio), do que mais rende para o que menos rende. Use para perguntas tipo "qual loja rende mais?".

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

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.6/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so safety is covered. The description adds useful behavioral value by enumerating the returned metrics and stating results are sorted by revenue descending, which it must do since there is no output schema, but it says nothing about default period behavior, empty-result handling, or whether all marketplaces are always returned.

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?

Two tight clauses with the core action and ranking order front-loaded; the parenthetical metric list is dense but earns its place given no output schema. Minor redundancy between 'compara lado a lado' and the ranking phrase.

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 read-only, zero-required-parameter comparison tool with a fully documented schema, the description covers what is compared and how results are ordered. Remaining gaps (period defaults, result shape) are either in the schema or low-risk, but with no output schema a word on coverage of marketplaces would have completed it.

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%, and the schema itself explains days as an alternative to start/end with a 30-day default. The description adds no parameter meaning beyond 'no período', so the 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 specific verb (compara) and resource (marketplaces) plus the exact metrics compared and the ordering ('do que mais rende para o que menos rende'). It implicitly separates itself from the dimension-breakdown siblings by being a cross-marketplace ranking, but never names or contrasts with them explicitly.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives a concrete usage trigger ('perguntas tipo "qual loja rende mais?"'), which tells the agent the question shape this tool answers. No when-not conditions or named alternatives (e.g. painel_compare_periods for time comparisons, painel_get_sales_summary for totals) are offered.

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