Skip to main content
Glama

Get inbox summary

get_inbox_summary
Read-only

Resumo das caixas de entrada das Conversas: para cada número de WhatsApp (pelo nome), o e-mail e o chat do site, quantas conversas estão abertas, quantas esperam resposta da equipe (o cliente falou por último, sem as concluídas e adiadas; e-mail só quando a conta já tinha escrito) e quantas dessas passaram de 24 horas. O número pessoal só aparece para quem o conectou, com incluir_pessoal=true. Responde "como estão as minhas caixas?".

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

Input Schema

NameRequiredDescriptionDefault
target_user_idNo(Só o admin da plataforma) userId da conta a operar
incluir_pessoalNotrue = inclui o número pessoal de quem está usando a chave

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.3/5.0
Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already cover the safety profile (readOnlyHint=true, destructiveHint=false, openWorldHint=false), so the bar is lower, and the description still adds real behavioral rules: concluded and postponed conversations are excluded, email threads count only when the account had already written, and the personal number is hidden unless connected. Return shape is described per channel, though ordering and exact field names are not.

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?

The resource is front-loaded and every clause carries information (metric definitions, exclusions, visibility rules). It is one long sentence with nested parentheticals that take effort to parse, which keeps it short of a 5.

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 parameter-light read-only tool with annotations and no output schema, the description supplies the counting semantics an agent needs to interpret results correctly, which is the main risk here. Minor gaps remain around result ordering and whether empty inboxes are included.

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 is 3; the description goes beyond it by explaining that the personal number appears only for users who actually connected it, which qualifies incluir_pessoal=true beyond the schema's phrasing. target_user_id's admin-only restriction is merely repeated from the schema.

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 states a specific verb and resource (an aggregated 'resumo' of the Conversation inboxes) and enumerates exactly what is counted per channel: open conversations, those awaiting a team reply, and those past 24 hours. That level of scope detail lets an agent distinguish it from a listing tool like list_inbox without opening the schema.

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?

The closing line 'Responde "como estão as minhas caixas?"' anchors the tool to a concrete intent, which is clear usage context. It stops short of naming an alternative or stating when not to use it (e.g., versus list_inbox or get_business_summary), so it is not a full 5.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources