Skip to main content
Glama

top_products

Read-onlyIdempotent

Rank products within a date range by revenue or quantity to identify sales leaders and compare performance.

Instructions

Produtos mais vendidos num período (datas AAAA-MM-DD), por faturamento ou quantidade.

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": {
      "start_date": "<start_date>",
      "end_date": "<end_date>"
    },
    "name": "top_products"
  }
}

Input Schema

NameRequiredDescriptionDefault
byNorevenue
limitNo
end_dateYes
start_dateYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, so the safety profile is covered. The description contributes the date format and the two ranking dimensions, but says nothing about ordering direction, how ties or limit truncation behave, or which date field the range applies to.

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?

One compact sentence with the core noun phrase front-loaded and the format and dimension options packed into parentheticals. Nothing is wasted, though the brevity comes at the cost of the missing parameter details.

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

Completeness3/5

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

An output schema exists, so return values need no explanation, and annotations cover safety. However, for a 4-parameter tool with 0% schema coverage, the description omits limit semantics and defaults, which are needed to call the tool precisely.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description carries the whole burden. It usefully specifies the AAAA-MM-DD format and the 'revenue' vs 'quantity' choice for `by`, but `limit` and the defaults (by=revenue, limit=5) are never mentioned, leaving half the parameters undocumented.

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?

The description states a specific resource and aggregation: the top-selling products over a period, ranked by revenue or quantity. An agent can tell what the tool returns, though it never contrasts itself with siblings like sales_summary or customer_orders.

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

Usage Guidelines2/5

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

There is no explicit when-to-use or when-not-to-use guidance, and no alternative is named. The period-ranking use case is only implied by the phrase 'num período', leaving the agent to infer routing versus sales_summary on its own.

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