Meta Council

Ticket Dependency Add

ticket_dependency_add

Record that an owned ticket cannot complete until another owned ticket is done. The edge is never erased: correct a mistake with ticket_dependency_remove, which marks the edge removed and appends to a ledger rather than deleting anything. Re-adding the same prerequisite reinstates that original edge instead of creating a second one, so an edge removed and restored says so. An edge stops blocking when the prerequisite reaches done, and only then — archiving the prerequisite does not release it. Only epics are gated, so an edge on a task is recorded and reported but never blocks its completion. Rejections carry a stable code: dependency_self (422), dependency_duplicate, dependency_cycle, dependency_graph_too_large (409), ticket_not_found (404).

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": {
      "ticket_id": "<ticket_id>",
      "depends_on_ticket_id": "<depends_on_ticket_id>"
    },
    "name": "ticket_dependency_add"
  }
}

Input Schema

Name	Required	Description	Default
`ticket_id`	Yes
`depends_on_ticket_id`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedSep 15, 2026

changedOutput schema / (root)

Previous value: -{
-  "additionalProperties": false,
-  "properties": {
-    "text": {
-      "type": "string"
-    }
-  },
-  "required": [
-    "text"
-  ],
-  "type": "object"
-}New value: +null

AddedAug 14, 2026

TDQS

A4.9/5.0

Behavior5/5

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

Beyond annotations (which only mark readOnly/destructive/idempotent false), the description reveals critical behavior: edges are never erased, re-adding reinstates the original edge, archiving does not release the dependency, and task-level edges are non-blocking. It also documents stable rejection codes, giving the agent a full behavioral contract.

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?

Every sentence in the description carries essential information—purpose, mutation semantics, idempotent-like re-add behavior, unblocking condition, epic-only gating, and error codes. It is dense but front-loaded with the core purpose, and no sentence is redundant.

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?

The description is thorough for a mutation tool with no output schema: it covers edge lifecycle, scope restrictions, and error codes. However, it does not describe the success return payload or explicitly define 'owned', so a small gap remains for agents that need to interpret the result.

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

Parameters5/5

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

Schema coverage is 0%, but the description compensates by defining the relationship: ticket_id is the dependent ticket, depends_on_ticket_id is the prerequisite. The mention of dependency_self and dependency_duplicate error codes clarifies that the IDs must be distinct and that duplicate edges are rejected, adding meaning beyond the bare UUID schema.

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?

The description states a specific action ('Record that an owned ticket cannot complete until another owned ticket is done') and clearly differentiates from the sibling ticket_dependency_remove by explicitly naming it as the correction path. This leaves no ambiguity about what the tool does.

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

Usage Guidelines5/5

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

It explicitly guides when to use this tool vs ticket_dependency_remove, explains the consequence of re-adding a prerequisite, and notes that only epics are gated, so the tool records but does not block for tasks. It provides clear context for the edge case of archiving and error codes.

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

All Meta Council tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?