Skip to main content
Glama
callcenter-kpi-mcp

callcenter-kpi-mcp

by jojao115

Mapa de calor de volume

volume_por_hora
Read-only

Calculates average calls opened per weekday and hour as a heat map and identifies peak times, filtered by company and queue, to help plan staffing schedules.

Instructions

Média de atendimentos abertos por dia da semana e hora do dia (mapa de calor), e o horário de pico. Serve para dimensionar escala. Filtra por empresa e por fila.

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

Input Schema

NameRequiredDescriptionDefault
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.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.9/5.0
Behavior3/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 the aggregation grain (weekday × hour) and that a peak hour is derived, but says nothing about return shape, units, or how empty days are handled.

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?

Three compact sentences with the metric, the output and the use case front-loaded; nothing redundant or padded.

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 aggregation with four optional parameters and no output schema, the description conveys what is computed conceptually (heatmap plus peak hour). It omits only minor details like the default date window, which the schema already covers.

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 would be 3, but the description adds real meaning by stating the filters are empresa and fila and that the tool aggregates a heatmap over a period. It does not restate date semantics, which the schema already documents well.

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 computation: average of opened tickets per weekday and hour (heatmap) plus the peak hour. That distinguishes it from previsao_volume (a forecast) without naming the sibling, so it is clear but not explicitly differentiated.

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

Usage Guidelines4/5

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

'Serve para dimensionar escala' gives a concrete use case (staffing/sizing), which tells the agent when this tool is the right one. There are no exclusions or named alternatives, so it stops short of full when-not guidance.

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