Skip to main content
Glama

ui_set_dep

Add or remove a dependency edge between tasks by specifying project, upstream, and downstream task IDs to define task order.

Instructions

App-only: add or remove a dependency edge between tasks.

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": {
      "project_id": "<project_id>",
      "upstream_id": "<upstream_id>",
      "downstream_id": "<downstream_id>"
    },
    "name": "ui_set_dep"
  }
}

Input Schema

NameRequiredDescriptionDefault
actionNo
project_idYes
upstream_idYes
downstream_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.7/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full burden of behavioral disclosure for a mutation tool. It does not say whether cycles or duplicate edges are rejected, whether removal needs both endpoint ids, whether the change is reversible, or what permissions are required — 'add or remove' is all the agent gets.

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?

A single short sentence with the qualifier front-loaded and no filler. It is efficient, though the terseness contributes to the gaps noted in other dimensions rather than reflecting deliberate prioritization.

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

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a four-parameter write operation with no annotations, no output schema, and zero schema description coverage, this definition is far too thin. The agent lacks the default action behavior, direction semantics for the two task ids, and any error or constraint behavior.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% across four parameters, so the description should compensate and does not. In particular, 'action' is optional in the schema yet the description never states a default, leaving the agent to guess whether omitting it adds or removes the edge; upstream/downstream direction semantics are also unstated.

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 pair (add/remove) and a specific resource (a dependency edge between tasks), so the operation is unambiguous. It does not name or contrast any sibling, but no sibling appears to overlap, so distinguishability is not a real problem.

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?

'App-only' is the only usage constraint given and it is left unexplained — the agent cannot tell what 'app-only' excludes or what the alternative path would be. There is no statement of when to prefer this tool over ui_move_task or task_update when restructuring work.

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