Skip to main content
Glama
Sign In
patchwork-os

patchwork-os

by Oolab-labs
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

ctxGetTaskContext

Read-only

Retrieve unified issue, PR, commit, or error context, including linked commits and related traces, in summary or full mode.

Instructions

Unified context for issue/PR/commit/error ref. Composes issue + linked commits + related traces. mode:'summary' (default) caps bodies; mode:'full' for untruncated. Prefer over gh/git.

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": {
      "ref": "<ref>"
    },
    "name": "ctxGetTaskContext"
  }
}

Input Schema

NameRequiredDescriptionDefault
refYesIssue (`#42` / `GH-42`), PR (`PR-42` / `pull/42`), commit SHA (7-40 hex), or Linear issue (`LIN-42` / `TEAM-123`). Whitespace-trimmed.
modeNoResponse verbosity. 'summary' (default) caps body fields at 500 chars and sets bodyTruncated:true. 'full' returns untruncated bodies. linkedIssueRefs on pullRequest is extracted from the raw body BEFORE truncation, so it is preserved in both modes.
maxLinkedCommitsNoCap on linked-commits section. Default 10.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.2.3
    • addedInput schema / properties / mode
      Added value: +{
+  "description": "Response verbosity. 'summary' (default) caps body fields at 500 chars and sets bodyTruncated:true. 'full' returns untruncated bodies. linkedIssueRefs on pullRequest is extracted from the raw body BEFORE truncation, so it is preserved in both modes.",
+  "enum": [
+    "summary",
+    "full"
+  ],
+  "type": "string"
+}
  2. First observedv1.0.0

TDQS

A4/5.0
Behavior3/5

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

readOnlyHint=true already tells the agent this is a safe read, and the composition/mode behavior is largely restated from the schema. The description adds the aggregation intent ('composes issue + linked commits + traces'), which is useful, but discloses nothing about auth, rate limits, or failure modes beyond what annotations and schema provide.

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?

Four short, front-loaded sentences with zero filler; purpose, behavior, and routing preference are all packed efficiently.

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?

No output schema exists, so the description carries the burden of describing returns; it names the composed sections (issue, linked commits, traces) and the truncation behavior, which is largely adequate. The precise return shape is not detailed, leaving a minor gap.

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 fully documents ref, mode, and maxLinkedCommits. The description only restates the mode enum semantics already in the schema and adds no syntax or format detail, so the baseline of 3 applies.

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?

'Unified context for issue/PR/commit/error ref' states a specific verb+resource, and 'Composes issue + linked commits + related traces' spells out exactly what the tool does and how it differs from a plain single-source fetch. An agent can distinguish it from siblings like fetchGithubIssue or getCommitsForIssue.

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?

'Prefer over gh/git' gives explicit alternative-routing guidance, which is clear context for when to reach for this tool. However, it does not differentiate from the many overlapping siblings in the list (fetchGithubIssue, getCommitsForIssue, ctxQueryTraces), so it falls short of full when/when-not coverage.

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