Skip to main content
Glama
callcenter-kpi-mcp

callcenter-kpi-mcp

by jojao115

Taxa de abandono

taxa_abandono
Read-only

Calculate call center abandonment rates and abandoned-call volumes by queue, hour, day, or company, showing where customers leave the queue.

Instructions

Volume, abandonos e taxa de abandono (% de clientes que desistiram na fila) por fila, hora do dia, dia ou empresa.

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

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.
agrupar_porNoPadrão: fila.fila
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

B3.2/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 meaningful semantic definition of the abandonment rate, but says nothing about the returned shape, default window behavior, or granularity limits. With annotations carrying the behavioral burden, this is adequate but thin.

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?

A single dense sentence with zero filler, front-loading the metrics before the grouping dimensions. It is efficient, though the flat list of metrics and dimensions gives little structural separation between what is returned and how it is sliced.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With five optional parameters and no output schema, the description should clarify what the response looks like (metric columns, per-group rows). It names the metrics but not the return structure or how volume and abandonos relate to the computed rate, leaving a real gap for a tool with 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 every parameter (including defaults for dates and the fila/empresa filter semantics) is already documented in the schema. The description only restates the grouping options already present in the enum, adding no new parameter 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 concrete metrics (volume, abandonos, taxa de abandono) and explicitly defines the rate as the percentage of clients who abandoned the queue, plus the four grouping dimensions. The purpose is unmistakable, though it never names a sibling tool to distinguish itself from volume_por_hora or tme_por_periodo.

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

Usage Guidelines2/5

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

There is no when-to-use guidance, no exclusions, and no reference to alternatives among the many sibling analytics tools. The only usage signal is the implicit one carried by the 'agrupar_por' options, leaving the agent to infer context from the tool name alone.

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