Skip to main content
Glama

sales_summary

Read-onlyIdempotent

Calculate revenue, order count, item count, and average ticket for a date range, grouped by total, month, category, or state.

Instructions

Faturamento, nº de pedidos, itens e ticket médio num período (datas AAAA-MM-DD, inclusivas).

group_by: 'total', 'month' (por mês), 'category' (por categoria) ou 'state' (por UF).

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": "sales_summary"
  }
}

Input Schema

NameRequiredDescriptionDefault
end_dateYes
group_byNototal
start_dateYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, so safety is covered; the description adds real context beyond that by stating the date format (YYYY-MM-DD), that bounds are inclusive, and exactly which metrics are computed. It omits currency, timezone and any row-limit behavior, so it is not fully rich but is well above the annotation baseline.

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?

Two short blocks with zero filler: the metric/period statement first, then the group_by enumeration on its own line. Every clause carries information an agent needs before calling.

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 simple three-parameter read tool with an output schema (so return shape need not be explained), the description covers period, metric set and grouping dimension. Minor gaps remain around currency/locale of 'Faturamento' and error behavior for malformed or inverted date ranges.

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

Parameters4/5

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

Schema description coverage is 0% — all three parameters carry only titles — so the description must compensate, and it does: it fixes the date string format and inclusivity for start_date/end_date and defines each group_by enum value, including that 'state' means UF. Only the default behavior of 'total' beyond the enum default in the schema is left implicit.

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 names a specific aggregation: revenue ('Faturamento'), order count, item count and average ticket over a date range, which is clearly a sales-summary operation. It does not differentiate itself from siblings like top_products, run_sql or customer_orders, though the metric set makes its scope distinguishable on inspection.

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 only implied: 'num período' plus the group_by enumerations tell the agent how to shape the query, but there is no statement of when to pick this over run_sql or top_products, nor any prerequisites. The group_by explanations ('por mês', 'por categoria', 'por UF') do give useful variant guidance within the tool itself.

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