Skip to main content
Glama
callcenter-kpi-mcp

callcenter-kpi-mcp

by jojao115

Detalhe de um atendimento

atendimento_detalhe
Read-only

Retrieves full details for a call center interaction by ID, including queue, agent, channel, timestamps, wait, duration, score, and the same customer's contacts within 7 days before and after.

Instructions

Mostra um atendimento pelo id: empresa, fila, operador, canal, motivo, horários, espera, duração e nota, e os contatos do mesmo cliente nos 7 dias antes e depois.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "id": "<id>"
    },
    "name": "atendimento_detalhe"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesId do atendimento.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.7/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 safety is covered. The description does add genuinely non-obvious behavior — the response expands beyond the single record to include the same customer's contacts within 7 days before and after — but says nothing about what happens with an invalid/nonexistent id or about result size limits.

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?

One front-loaded sentence with the verb and key first, then the returned fields. The field enumeration is long but earns its place because there is no output schema to describe the payload; only mild redundancy with 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?

With no output schema, the description carries the return-value burden and does so thoroughly, including the extra ±7-day contacts. What is missing is edge-case behavior for unknown ids and whether the time window is relative to the atendimento date — minor for a simple read tool whose annotations already signal a safe, closed-world read.

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% ("Id do atendimento."), so the single parameter is fully documented structurally. The description confirms the id is the atendimento key but adds no format, range, or resolution detail beyond the schema; baseline 3 applies for a one-parameter tool.

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?

States a specific verb and resource ("Mostra um atendimento pelo id") and then enumerates exactly which fields come back (empresa, fila, operador, canal, motivo, horários, espera, duração, nota) plus the ±7-day related contacts. This makes it unmistakably a single-record lookup, clearly distinct from the aggregate/ranking siblings like tme_por_periodo or ranking_operadores.

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 only implied: the "pelo id" framing tells the agent it needs a specific atendimento id, and the ±7-day contact window hints at recurrence investigations. There is no explicit when-to-use statement, no exclusions, and no pointer to a sibling for aggregate questions.

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