Skip to main content
Glama
callcenter-kpi-mcp

callcenter-kpi-mcp

by jojao115

Empresas, filas e período disponível

listar_empresas
Read-only

Lists companies, their queues with IDs, active operator counts, and available data date ranges so you can discover valid queue IDs and query dates before running KPI reports.

Instructions

Lista as empresas atendidas, as filas de cada uma (com ids), quantos operadores ativos há e o primeiro e o último dia com dados. Chame primeiro para descobrir ids e datas válidas.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.4/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 behavior beyond that: the response is a discovery payload containing ids and valid date boundaries, and the tool is intended as the first call in a workflow — context the annotations do not convey. Pagination and result-size behavior are unstated, but with zero parameters there is little risk surface.

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, both load-bearing: the first enumerates the payload, the second states the calling convention. The most actionable instruction ('call first') is placed last as a clear directive with no filler or redundant restatement of the title.

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?

There is no output schema, so the description carries the burden of describing return values — and it does, listing the four main result elements. It does not specify nesting/shape or whether the date range is global or per-company, which is a minor residual gap for a discovery tool this simple.

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?

The tool takes no parameters, so the baseline of 4 applies. The empty object schema is fully consistent with the description, which correctly implies the call needs no input to return the full company/queue/date inventory.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names a specific verb ('Lista') and enumerates exactly what is returned: companies, their queues with ids, active operator counts, and the first/last day with data. That output inventory makes it immediately distinguishable from the analytics siblings (tme_por_periodo, taxa_abandono, etc.), which compute metrics rather than expose catalog metadata.

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?

'Chame primeiro para descobrir ids e datas válidas' gives explicit sequencing guidance: call this before the analytical tools, for the purpose of obtaining valid ids and date bounds. What is missing is a named alternative or an explicit 'do not use this for metrics' exclusion, which keeps it short of a 5.

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