Skip to main content
Glama
callcenter-kpi-mcp

callcenter-kpi-mcp

by jojao115

Rechamadas

rechamadas
Read-only

Identifies repeat customer contacts within a set time window and groups them by operator, queue, or company to reveal unresolved issues and prioritize follow-up.

Instructions

Quantos atendimentos finalizados tiveram rechamada: o mesmo cliente voltou a abrir atendimento dentro da janela de horas. Rechamada alta indica problema não resolvido. Agrupa por operador (quem atendeu o primeiro contato), fila ou empresa, do maior número para o menor.

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

Input Schema

NameRequiredDescriptionDefault
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.
agrupar_porNoPadrão: operador.operador
data_inicioNoPrimeiro dia, AAAA-MM-DD (fuso de São Paulo). Padrão: 7 dias antes de data_fim.
janela_horasNoJanela depois do fim do atendimento, em horas (1 a 168). Padrão: 24.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.7/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 the safety profile is covered. The description adds genuine domain context beyond that: the operational definition of a 'rechamada', the interpretation of high values, and that output is sorted descending by group size.

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?

Three tight sentences: metric definition first, then interpretation, then grouping and sort behavior. The semicolon-heavy phrasing is dense but nothing is redundant.

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 aggregate tool with no output schema, the description covers what is computed, how results are grouped, and the sort order, while the schema fully handles parameters and defaults. Only explicit sibling routing is absent.

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 coverage is 100%, so every parameter (limite, fila_id, empresa_id, datas, agrupar_por, janela_horas) is already documented in the schema. The description reinforces what agrupar_por and janela_horas mean but adds little syntax or constraint detail beyond it; 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?

The description names the exact metric — count of finalized atendimentos that had a callback where the same client reopened a session inside the hours window — and states the grouping dimensions. This is specific and distinct from siblings like tme_por_periodo or taxa_abandono, though it never explicitly contrasts itself with them.

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 implied through interpretation guidance ('Rechamada alta indica problema não resolvido'), which tells an agent the analytical question this answers. There is no explicit when-to-use/when-not or named alternative among the siblings, so the routing has to be inferred.

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