Skip to main content
Glama

Get funnel flow

get_funnel_flow
Read-only

Fluxo de um funil no período: quantos contatos diferentes ENTRARAM em cada etapa (na ordem), o % em relação à etapa anterior, ganhos, perdidos à parte e a conversão total (ganhos ÷ quem entrou na primeira etapa). Usa o histórico de etapas, que existe desde 12/11/2026: períodos antes disso vêm zerados. Padrão: últimos 30 dias. funil="todos" (ou sem funil numa conta com vários) = visão global: cada funil numa linha, os comerciais somados num total com setup e mensalidade separados, os de operação à parte (concluídos, em andamento, parados). Cada etapa traz foram_para_outro_funil (quem saiu dela para outro funil no período: continua em "entraram", mas sai do % da etapa seguinte, do gargalo e da conversão) e agora (contatos na etapa hoje); o funil traz tipo (comercial/operacao) e etapas_perdidas com o agora.

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_funnel_flow"
  }
}

Input Schema

NameRequiredDescriptionDefault
deNoDia inicial AAAA-MM-DD (Brasília). Padrão: 30 dias atrás
ateNoDia final AAAA-MM-DD (Brasília). Padrão: hoje
funilNoFunil (id ou nome), ou "todos" para a visão global. Sem funil numa conta com vários: visão global.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / funil / description
      Previous value: -"Funil (id ou nome). Obrigatório se a conta tiver mais de um."New value: +"Funil (id ou nome), ou \"todos\" para a visão global. Sem funil numa conta com vários: visão global."
  2. Added

TDQS

A4.5/5.0
Behavior5/5

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

Annotations already cover the safety profile (readOnly, non-destructive, closed-world), and the description adds substantial behavioral context beyond them: the data-availability cutoff that silently zeroes older periods, the default date window, how multi-funnel accounts are aggregated (commercial totals with setup and monthly fee separated, operations grouped by concluded/in-progress/stalled), and the foram_para_outro_funil edge case that keeps a contact in "entraram" while removing it from the next stage's %, bottleneck, and conversion.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The purpose is front-loaded in the first clause, but the body is a dense run-on that mixes computation semantics, data caveats, aggregation rules, and per-field return documentation in one block. Every piece is relevant, yet the absence of structure (no separation of inputs vs. outputs vs. caveats) makes it harder to scan than its length warrants.

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

Completeness5/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 full burden of explaining return shape — and it does, covering stage-level fields (foram_para_outro_funil, agora), funnel-level fields (tipo, etapas_perdidas), and the global view's row layout. Combined with the history cutoff and default window, an agent has everything needed to call it and interpret the result.

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, but the description adds meaning the schema only hints at: what "todos" actually produces (one funnel per row, totals split by type) and what happens when funil is omitted on a multi-funnel account, plus the Brasília-timezone day-based window. It does not add format detail for the id-or-name ambiguity of the funil parameter beyond what the schema states.

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 resource (funnel flow) and enumerates exactly what it computes: distinct contacts entering each stage in order, the percentage versus the prior stage, won/lost counts separately, and total conversion (won ÷ first-stage entries). It also disambiguates the two modes (single funnel vs. funil="todos" global view), so an agent can distinguish this from the other get_* tools 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?

It states the default window (last 30 days) and the condition that triggers the global view ("funil='todos', or omitted on an account with multiple funnels"), plus a hard availability constraint (stage history only exists from 12/11/2026; earlier periods come back zeroed). It does not name alternative tools for related analyses, but the when-to-use conditions for its own modes are explicit.

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