Skip to main content
Glama

set_dependencies

Defines which features must finish before a given feature can start, blocking it until all listed dependencies are completed.

Instructions

Set dependencies for a feature. The feature cannot be started until all its dependencies are completed.

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": {
      "projectDir": "<projectDir>",
      "featureId": "<featureId>",
      "dependsOn": "<dependsOn>"
    },
    "name": "set_dependencies"
  }
}

Input Schema

NameRequiredDescriptionDefault
dependsOnYesArray of feature IDs this feature depends on
featureIdYesID of the feature to set dependencies for
projectDirYesAbsolute path to the project directory

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.3/5.0
Behavior3/5

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

With no annotations, the description carries full behavioral burden, and it does disclose one meaningful consequence: the feature is blocked until all dependencies complete. However, it never says whether existing dependencies are replaced or merged, how invalid or cyclic IDs are handled, or whether the call fails when a dependency is already completed.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two short sentences with the action first and the consequence second; there is no filler or redundant restatement of the name.

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

Completeness3/5

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

For a three-parameter mutation tool with no annotations and no output schema, the definition covers purpose and blocking semantics but leaves the critical replace-vs-append behavior and error outcomes unexplained.

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% and all three parameters are self-documented, so the baseline applies. The description adds no meaning beyond the schema, e.g. whether dependsOn replaces the current list or appends to it.

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 and resource ('Set dependencies for a feature'), and the second sentence clarifies the resulting constraint. It does not explicitly contrast with siblings such as get_feature_graph or add_feature, so sibling differentiation is left to the agent.

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 guidance on when to call this versus inspecting the graph first, nor any prerequisite such as the features already existing or an approved plan. Usage is only implied by the verb.

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