Skip to main content
Glama

Meilleurs clients

get_top_customers
Read-onlyIdempotent

Meilleurs clients par chiffre d'affaires sur une période en jours (ventes en caisse + factures définitives, comme le module Rapports). (Lecture seule.)

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

Input Schema

NameRequiredDescriptionDefault
daysNoPériode : les N derniers jours, aujourd'hui compris (défaut 30).
limitNoNombre de clients renvoyés (défaut 10).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/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 the safety profile is covered. The description adds real behavioral context beyond that: the figures aggregate cash-register sales plus final invoices and match the Reports module, which tells the agent what counts toward revenue and why numbers may differ from raw sale listings. The trailing '(Lecture seule.)' merely repeats the annotation.

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 front-loaded sentence carries the metric, scope, and data sources, followed by a short parenthetical. The read-only parenthetical duplicates structured annotation data and is the only wasted fragment.

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 two-parameter, zero-required analytics read with full annotation coverage, the definition supplies enough to call it correctly. Minor gaps remain: no indication that results are ordered descending by revenue or what fields each customer entry contains, which matters slightly since there is no output schema.

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 both 'days' and 'limit' are already fully documented with defaults. The description's phrase 'sur une période en jours' reinforces 'days' but adds no new syntax, bounds, or edge-case meaning. 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 resource (top customers), the ranking metric (revenue) and the time window, which clearly separates it from get_top_products. It never names a sibling explicitly, so differentiation comes from the resource noun rather than an explicit contrast.

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: an agent can infer this is the tool for a ranked customer-by-revenue view, but there is no statement of when to prefer it over search_customers, get_customer, or get_sales_report. No exclusions or prerequisites are given.

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