Skip to main content
Glama
callcenter-kpi-mcp

callcenter-kpi-mcp

by jojao115

Ranking de operadores

ranking_operadores
Read-only

Ranks call center operators by volume, TMA, TME, or CSAT over a date range, returning all four metrics per operator with optional company and queue filters.

Instructions

Ranking de operadores por volume atendido, TMA, TME ou CSAT, com os quatro números de cada um. Ordem desc = do maior para o menor (para "mais rápido" em TMA use asc).

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

Input Schema

NameRequiredDescriptionDefault
ordemNoPadrão: desc.desc
limiteNoMáximo de linhas na resposta. Padrão: 10.
fila_idNoFiltra uma fila (suporte, financeiro, comercial). Os ids saem de listar_empresas.
data_fimNoÚltimo dia, incluído, AAAA-MM-DD. Padrão: ontem.
empresa_idNoFiltra uma empresa. Sem ele, soma todas. Os ids saem de listar_empresas.
data_inicioNoPrimeiro dia, AAAA-MM-DD (fuso de São Paulo). Padrão: 7 dias antes de data_fim.
ordenar_porNoPadrão: volume.volume

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=true and openWorldHint=false, so safety is covered. The description adds value beyond that by disclosing the shape of the result ('com os quatro números de cada um'), which matters since there is no output schema, and by explaining the sort-direction semantics. It stops short of covering anything about aggregation across queues/companies or empty results.

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 sentences with no waste; the metric scope and the returned numbers come first, and the ordering caveat follows. Every clause carries information an agent needs.

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 seven all-optional parameters, no output schema, and no required arguments, the description supplies the two things the schema cannot: what a row contains and how sort direction interacts with metric semantics. What remains uncovered (default window behavior, aggregation semantics when empresa_id is omitted) is already documented in the parameter descriptions.

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 coverage is 100%, so the baseline is 3, but the description adds real meaning the schema's 'Padrão: desc' does not: that desc means greatest-to-least, and that 'fastest' on TMA requires asc because lower TMA is better. That inversion is exactly the kind of trap an agent would otherwise fall into.

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 and operation: an operator ranking over one of four named metrics (volume, TMA, TME, CSAT), plus the notable detail that all four numbers are returned per operator. It does not name or distinguish itself from near siblings like csat_por_operador or tme_por_periodo, so it falls short of a 5.

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 one piece of real guidance is directional: desc means largest-to-smallest and asc should be used for 'fastest' on TMA, which is a genuine usage hint. However, there is no explicit when-to-use/when-not guidance relative to alternatives such as csat_por_operador, which also reports a per-operator metric, so usage is only implied.

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