Skip to main content
Glama

Update goal

update_goal
DestructiveIdempotent

Muda uma meta (alvo, nome, inicio, fim, funil, etapa, visibilidade, no_inicio) ou arquiva (arquivar: true) / volta (desarquivar: true). Arquivar não apaga.

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

Input Schema

NameRequiredDescriptionDefault
idYesID da meta (list_goals)
fimNoAAAA-MM-DD
alvoNoNovo alvo
nomeNoNovo nome
etapaNoEtapa (id ou nome); "" tira o filtro
funilNoFunil (id ou nome); "" tira o filtro
inicioNoAAAA-MM-DD
arquivarNotrue arquiva
no_inicioNoMostra no Início
desarquivarNotrue volta a meta
visibilidadeNoQuem vê

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true and idempotentHint=true, so the safety profile is known. The description adds genuinely useful context beyond that: 'Arquivar não apaga' tells the agent archiving is reversible non-deletion, which softens and clarifies the destructive flag. It does not mention permission requirements or what the response contains.

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 compact sentence, front-loaded with the mutation and its field list, then the archive/restore alternatives, then the non-deletion caveat. No wasted wording, though cramming eight field names into parentheses is dense.

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 an 11-parameter mutation tool with full schema coverage, no output schema, and existing annotations, the description covers the mutation surface and the archive semantics well. It leaves implicit whether omitted fields stay unchanged and what the call returns, which are minor residuals.

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%, so all 11 parameters are already documented, and the description largely restates the same field names the schema lists. The only added meaning is the archive/restore pairing, so the baseline 3 applies rather than a higher score.

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?

States a specific verb ('Muda' / 'arquiva' / 'volta') applied to a named resource ('uma meta') and enumerates exactly which fields can change. It clearly separates the create path (sibling create_goal) from the mutation path, though no sibling is named explicitly.

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?

Gives concrete how-to guidance for the two non-obvious modes ('arquivar: true' archives, 'desarquivar: true' restores), which is more than nothing. But it never says when an agent should prefer this over archive_conversation-style siblings or when not to use it, and no prerequisites are stated.

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