Skip to main content
Glama
Sign In

Radar noEixo

by com.noeixodigital
OverviewDiscussionsAdmin

Update process step

update_process_step
DestructiveIdempotent

Atualiza um passo do processo: status (pending → in_progress → done, blocked, ou skipped = pulada, que conta como resolvida sem disparar o gatilho de etapa concluída), data limite (due_date, fixa à mão; as etapas seguintes passam a contar dela) e responsável. Tudo vai para o histórico do processo, com o motivo se informado.

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

Input Schema

NameRequiredDescriptionDefault
motivoNoPor que mudou (vai para o histórico)
statusNoNovo status
step_idYesID do passo (via get_process)
due_dateNoNova data limite (AAAA-MM-DD). Vazio = sem prazo.
responsavel_idNoNovo responsável (id da equipe). Vazio = ninguém.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changed
    • addedInput schema / properties / due_date
      Added value: +{
+  "description": "Nova data limite (AAAA-MM-DD). Vazio = sem prazo.",
+  "type": "string"
+}
    • addedInput schema / properties / motivo
      Added value: +{
+  "description": "Por que mudou (vai para o histórico)",
+  "type": "string"
+}
    • addedInput schema / properties / responsavel_id
      Added value: +{
+  "description": "Novo responsável (id da equipe). Vazio = ninguém.",
+  "type": "string"
+}
    • changedInput schema / properties / status / enum
      Previous value: -[
-  "pending",
-  "in_progress",
-  "done",
-  "blocked"
-]New value: +[
+  "pending",
+  "in_progress",
+  "done",
+  "blocked",
+  "skipped"
+]
    • changedInput schema / required
      Previous value: -[
-  "step_id",
-  "status"
-]New value: +[
+  "step_id"
+]
  2. First observed

TDQS

A3.6/5.0
Behavior4/5

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

Beyond the annotations (destructiveHint, idempotentHint), the description discloses real behavioral consequences: 'skipped' counts as resolved without firing the step-completed trigger, and a manually set due_date becomes the reference for downstream steps. It also states that every change is written to the process history with the reason. It does not explain why the operation is flagged destructive or how errors/unknown status transitions are handled.

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 single dense sentence with parenthetical qualifiers, front-loading the resource and the mutable fields. It is information-rich with little waste, though the nested parentheses make it slightly harder to parse at a glance.

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?

With no output schema and a mutation that affects downstream steps, the description covers the important side effects (status semantics, due_date propagation, history logging). It is nearly complete for its complexity, missing only guardrails such as permission requirements or failure behavior.

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 genuine meaning: the status progression semantics, the special behavior of 'skipped', and the fact that due_date is set manually and re-anchors subsequent steps. The reason field's role in history is also clarified. Only the empty-string reset conventions are left to 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?

The description names a specific verb and resource ('Atualiza um passo do processo') and enumerates the three mutable facets: status, due_date, and responsável. It is clearly distinguishable from get_process/create_process, though it does not explicitly contrast with any sibling by name.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no explicit guidance on when to use this tool versus alternatives, nor any stated preconditions (e.g., that step_id comes from get_process, which only appears in the schema). Usage is implied by the verb but never framed as when/when-not.

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

All Radar noEixo toolsInspect
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