Skip to main content
Glama

Onplana

by io.github.Onplana
OverviewDiscussionsAdmin

link_dependency

DestructiveIdempotent

Create a dependency between two tasks. Type is one of FINISH_TO_START (default, successor starts when predecessor finishes), START_TO_START, FINISH_TO_FINISH, START_TO_FINISH. Lag defaults to integer days; pass lagUnit "hours" or "minutes" for a finer lag (stored to the minute, applied to the schedule at whole-day resolution for now). Negative values create lead time (successor starts before predecessor finishes). One pair may hold several types at once (e.g. an SS and an FF); the SAME type twice is refused. The server rejects self-dependencies and cyclic chains, and surfaces a clear error if the dependency graph is too large to validate safely. Both tasks must be visible to you. Re-linking the same type with the same lag succeeds as a no-op (alreadyLinked: true); the same type with a different lag is refused with the existing edge named. The two tasks may sit in different projects: the successor is then scheduled after the predecessor, the response carries crossProject: true, and the constraint runs one way, since the predecessor project is scheduled without reference to the successor project. rescheduled counts the tasks the link moved; in a project with automatic scheduling off it is 0 and the response carries autoScheduleOff: true, because there only Recalculate moves dates.

Input Schema

NameRequiredDescriptionDefault
lagNoLag amount in lagUnit. Default 0. Negative for lead time.
typeNoDefault FINISH_TO_START. Use FINISH_TO_FINISH for "wait for predecessor to wrap before declaring this done."
dryRunNoPreview only: report the would-be link (type, lag) plus wouldCreateCycle / alreadyExists flags, without committing. Writes nothing.
lagUnitNoUnit for lag: days (default), hours, or minutes.
successorIdYesTask that depends on the predecessor.
predecessorIdYesTask that must complete (or start, depending on type) first.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / lag / description
      Previous value: -"Integer days. Default 0. Negative for lead time."New value: +"Lag amount in lagUnit. Default 0. Negative for lead time."
    • addedInput schema / properties / lagUnit
      Added value: +{
+  "description": "Unit for lag: days (default), hours, or minutes.",
+  "enum": [
+    "days",
+    "hours",
+    "minutes"
+  ],
+  "type": "string"
+}
  2. Added

TDQS

A4.6/5.0
Behavior5/5

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

Goes well beyond the annotations (readOnlyHint=false, destructiveHint=true, idempotentHint=true), disclosing refusal conditions (self-dependencies, cycles, duplicate same-type), no-op idempotency for identical re-links, the one-way cross-project constraint, and the autoScheduleOff/rescheduled behavior.

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?

Dense but front-loaded with the core action and type list; the extended edge-case clauses are informative rather than filler. Slightly long, but nearly every sentence adds actionable detail.

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

Completeness5/5

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

With no output schema, the description still names the return fields (alreadyLinked, crossProject, rescheduled, autoScheduleOff) and covers error/cross-project/auto-scheduling cases an agent needs to interpret results.

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% (baseline 3), and the description adds genuine meaning: lag default and negative-as-lead-time, lagUnit resolution ('stored to the minute, applied at whole-day resolution'), plus per-enum type semantics. This exceeds what the schema documents.

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

Purpose5/5

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

States a specific verb+resource ('Create a dependency between two tasks') and immediately delimits it by type, lag, and constraints. Clearly differentiable from update_dependency, unlink_dependency, and propose_dependency, which handle modification, removal, and proposal respectively.

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

Usage Guidelines4/5

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

Gives extensive when-to-use guidance: dryRun for preview, lagUnit for finer lags, and the four type semantics with a default. It does not explicitly route to siblings (e.g. use update_dependency to change an existing link), but the conditional behaviors are unusually rich.

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

All Onplana toolsInspect
Try in Browser
Pay for results, not tokens.Fund a bounty. Let AI agents compete and collaborate to solve your problems.agentbounties.appAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources