Skip to main content
Glama
callcenter-kpi-mcp

callcenter-kpi-mcp

by jojao115

Previsão de volume

previsao_volume
Read-only

Forecasts upcoming call volume by averaging the last weeks for the same weekday, starting from the latest day with data. Returns the minimum and maximum of the history used to show expected variation.

Instructions

Prevê o volume de atendimentos dos próximos dias pela média das últimas semanas no mesmo dia da semana (média móvel simples), a partir do último dia com dados. Mostra o mínimo e o máximo do histórico usado, para dar a ideia da variação.

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

Input Schema

NameRequiredDescriptionDefault
fila_idNoFiltra uma fila (suporte, financeiro, comercial). Os ids saem de listar_empresas.
empresa_idNoFiltra uma empresa. Sem ele, soma todas. Os ids saem de listar_empresas.
dias_a_frenteNo1 a 14. Padrão: 7.
semanas_historicoNoSemanas de histórico na média, 1 a 12. Padrão: 4.

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 real behavioral value: the averaging method, the anchor point (last day with data), and that the result includes the historical min/max to convey variability. It does not mention rate limits or accuracy caveats, but this is solid beyond-annotation disclosure.

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 sentences, zero filler: method and anchor point first, then what the response conveys. Front-loaded and every clause earns its place.

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 no output schema, the description properly compensates by explaining that the response includes min and max of the history used. All four parameters are optional and fully documented in the schema. Only minor gaps remain, such as how defaults combine with filters.

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 3 is the baseline. The description reinforces the meaning of the two window parameters — the history window feeds the weekday average and the horizon is the forecast span — giving conceptual context the schema's terse field descriptions do not.

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 verb ("Prevê") and resource ("volume de atendimentos dos próximos dias"), plus the exact method (média móvel simples por dia da semana). The future-facing framing implicitly separates it from historical siblings like volume_por_hora, but no sibling is named explicitly.

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 by "próximos dias" — clearly a forecasting tool rather than a historical report. However, it never states when to prefer it over alternatives, nor any prerequisites or exclusions, leaving the agent to infer context.

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