Skip to main content
Glama

Create goal

create_goal

Cria uma meta. metrica: chave de list_goal_metrics. alvo: número (percentual até 100; minutos para primeira_resposta). inicio e fim: AAAA-MM-DD (Brasília). funil e etapa: id ou nome (só nas métricas que aceitam). visibilidade: gestao (dono e gerentes, padrão) | equipe | eu. no_inicio: mostra o cartão no Início (padrão true).

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": {
      "metrica": "<metrica>",
      "alvo": "<alvo>",
      "inicio": "<inicio>",
      "fim": "<fim>"
    },
    "name": "create_goal"
  }
}

Input Schema

NameRequiredDescriptionDefault
fimYesAAAA-MM-DD
alvoYesNúmero a atingir
nomeNoNome da meta (padrão: o da métrica)
etapaNoEtapa (id ou nome), para chegaram_na_etapa
funilNoFunil (id ou nome), quando a métrica aceita
inicioYesAAAA-MM-DD
metricaYesChave da métrica (list_goal_metrics)
no_inicioNoMostra no Início (padrão true)
visibilidadeNoQuem vê

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.6/5.0
Behavior3/5

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

The annotations already disclose this is a non-destructive, non-open-world write, so safety is covered. The description usefully adds undocumented defaults: visibilidade defaults to gestao and no_inicio defaults to true, and nome falls back to the metric name. It does not say what happens when an invalid metrica is sent or what the created goal looks like.

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?

It is a dense, front-loaded parameter glossary beginning with the action, with each fragment carrying constraint information and no filler. The telegraphic style is efficient, though a single lead sentence on when to use it would have earned its place.

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 nine-parameter mutation with no output schema and light annotations, the description covers every parameter, its format, its defaults, and the metric-specific constraints. Remaining gaps are error behavior and duplicate handling, which are secondary for a create tool.

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 genuinely adds meaning beyond the terse schema strings: alvo is a percentage capped at 100 or minutes for primeira_resposta, dates are Brasília time, funil/etapa accept id or name and only for certain metrics, and visibilidade's gestao is defined as owner and managers. Only the nome default overlaps with the schema.

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

Purpose4/5

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

"Cria uma meta" states a specific verb and resource, and the definition ties the metrica parameter to the sibling list_goal_metrics, which clarifies the create workflow. It does not explicitly distinguish itself from update_goal, but the creation intent is unambiguous.

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?

The definition implies usage by telling the agent that metrica must be a key from list_goal_metrics and that funil/etapa apply only to metrics that accept them. It gives no explicit when-to-use versus when-to-update guidance and no stated prerequisites such as needing a metric to exist first, leaving the agent to infer the context.

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