Skip to main content
Glama
delega-dev

delega-mcp

by delega-dev
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

link_task

Attach a branch, commit, PR, or URL to a task so repository work and external artifacts stay with the task's context.

Instructions

Attach a branch, commit, pull request, or URL link to a task. Use this when work in a repo, PR, or external artifact should travel with the task.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
refYesBranch name, commit SHA, PR number, or URL reference
urlNoOptional URL for the link
kindYesLink kind: branch, commit, pr, or url
repoNoRepository slug in owner/name form, when applicable
task_idYesThe task ID to link

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv1.19.0
    • removedInput schema / properties / task_id / anyOf
      Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "number"
-  }
-]
    • addedInput schema / properties / task_id / type
      Added value: +[
+  "string",
+  "number"
+]
  2. Addedv1.9.0

TDQS

A3.7/5.0
Behavior3/5

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

With no annotations provided, the description carries the full burden. It implies a write operation (attaching a link) but does not disclose whether it requires specific permissions, whether links are idempotent, or what happens on duplicate links. It adds some context but falls short of rich behavioral disclosure.

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 concise sentences, front-loading the action and then the usage scenario. No wasted words.

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 5-parameter mutation tool with no annotations and no output schema, the description is adequate but incomplete. It doesn't cover return values, error conditions, or behavioral details like idempotency, which are important for correct invocation.

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 the schema already documents all parameters thoroughly. The description lists the types of links (branch, commit, PR, URL) which aligns with the 'kind' enum but adds no new semantic meaning beyond 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 states a specific verb (attach) and resource (branch/commit/PR/URL link to a task), which is clear and distinct from sibling tools like list_task_links. However, it doesn't explicitly differentiate itself from list_task_links or other task-related tools beyond the linking action.

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?

It provides a clear usage context ('when work in a repo, PR, or external artifact should travel with the task'), but does not mention when not to use it or name alternatives like list_task_links for viewing links.

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

Deploy Server

Other Tools