Skip to main content
Glama

link_tickets

Connect a project to Linear or GitHub to sync Tares ticket list and enable milestone and ticket creation.

Instructions

Tie the project to where its tickets live, integration "linear" or "github" (Jira is not covered). link_fields holds only non-secret fields: for Linear project, the Linear project's id, URL or name; for GitHub repo (owner/name or URL) and issue_label (default tares:<project name>). The cell's own Linear or GitHub connection is used, so never pass a key or a token (it is refused). Tares then keeps its ticket list in sync (about once a minute) and reads it once now. After it, write_milestone and write_ticket create the milestones and tickets in Linear or GitHub. Returns the link and the tickets found.

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": {
      "integration": "<integration>"
    },
    "name": "link_tickets"
  }
}

Input Schema

NameRequiredDescriptionDefault
projectNo
integrationYes
link_fieldsNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.57.0

TDQS

A4.3/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does substantial work: it discloses the auth model (the cell's own Linear/GitHub connection is used, secrets are refused), the side effect of ongoing sync at roughly one-minute intervals, an immediate read, and the return payload. It does not say whether an existing link is overwritten or how permission failures surface, leaving some mutation behavior undisclosed.

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?

The action and its constraints are front-loaded, and each sentence contributes something distinct (scope, field shapes, auth rule, sync behavior, follow-on tools, return value). It is dense and slightly run-on with mid-sentence backticked identifiers, but there is no filler to cut.

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?

For a three-parameter mutation tool with no annotations, the definition covers the important unknowns: auth, side effects, sync cadence, integration-specific field shapes, and the workflow it unlocks. Since an output schema exists, the single sentence about return values is sufficient. The residual gap is the unexplained `project` parameter and re-link/overwrite 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 description coverage is 0%, so the description must compensate, and it largely does: `integration` values are enumerated inline, and `link_fields` is explained per integration (Linear `project` accepts id, URL or name; GitHub takes `repo` as owner/name or URL and `issue_label` defaulting to `tares:<project name>`), plus the non-secret restriction. The `project` parameter itself is never explained — only implied by 'Tie the project' and its empty default — which keeps this below a 5.

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 and resource — 'Tie the project to where its tickets live' — and immediately narrows scope with the accepted `integration` values ("linear" or "github") plus an explicit exclusion (Jira is not covered). It also positions itself relative to siblings by naming write_milestone and write_ticket as the downstream steps, so an agent can place it in the workflow without opening another schema.

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 clear ordering context: this tool links first, then write_milestone and write_ticket create the milestones and tickets in the linked system. It also states a hard constraint on invocation ('never pass a key or a token (it is refused)'). It stops short of stating when *not* to call it (e.g. what happens if the project is already linked), so it is clear but not exhaustive.

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