Radar noEixo

Create pipeline

create_pipeline

Cria um funil novo (ex.: "RH · Recrutamento"), que já nasce com etapas: comercial = Novo Lead, Qualificado, Em Proposta, Ganho, Perdido; operacao = Entrada, Em andamento, Concluído, Encerrado sem concluir. Funil de operação não conta como venda: a etapa final abre o processo (se tiver template) sem registrar negócio ganho nem disparar "deal_won". Precisa do recurso "Vários funis" (faixas Operação e Escala).

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": {
      "name": "<name>"
    },
    "name": "create_pipeline"
  }
}

Input Schema

Name	Required	Description
`name`	Yes	Nome do funil (até 60 letras)
`tipo`	No	comercial (vendas) ou operacao (RH, suporte, energia, obra). Padrão: comercial
`color`	No	Cor em hex (ex.: "#8b5cf6")

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 7, 2026

TDQS

A4.5/5.0

Behavior5/5

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

Annotations only declare it is a non-read-only, non-destructive local write. The description goes well beyond that: it discloses the default stage sets that will exist after creation, that operation funnels do not count as a sale, that the terminal stage opens a process when a template exists without registering a won deal or firing 'deal_won', and that a specific subscription feature is required.

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?

Dense but front-loaded: creation, default stages, semantic caveat about operation funnels, and the plan requirement appear in that order with no filler. A single paragraph carries a lot, though the stage listings make it wordier than strictly necessary.

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 three-parameter creation tool with no output schema, the description covers prerequisites, defaults, and side effects well. The only remaining gap is what the call returns (e.g., the new pipeline identifier) for chaining into create_pipeline_stage.

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; however the description adds genuine meaning by illustrating the funnel naming convention with a concrete example and by explaining the downstream consequences of the 'tipo' choice rather than just restating the enum values.

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 ('Cria um funil novo') and immediately disambiguates it from related siblings by explaining that the funnel is created already populated with stages, naming the exact default stages for both variants. An agent can tell this apart from create_pipeline_stage and create_process without opening any 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?

Gives clear selection guidance between the two funnel types ('comercial' vs 'operacao', with operation examples like RH, suporte, energia, obra) and states a hard prerequisite (the 'Vários funis' feature, Operação/Escala tiers). It stops short of explicitly naming alternatives such as create_process or create_pipeline_stage for related needs.

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

All Radar noEixo tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?