GitMem

Official

Overview Schema Source Related Servers Discussions Admin

create_thread

Create an open thread to track unresolved work across sessions. Uses semantic dedup to return existing similar threads, avoiding duplicates.

Instructions

Create an open thread to track unresolved work across sessions. Includes semantic dedup: if a similar open thread exists (cosine similarity > 0.85), returns the existing thread instead. Check the 'deduplicated' field in the response.

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": {
      "text": "<text>"
    },
    "name": "create_thread"
  }
}

Input Schema

Name	Required	Description	Default
`text`	Yes	Thread description — what needs to be tracked or resolved
`linear_issue`	No	Associated Linear issue (e.g., PROJ-123)

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.6.4Jun 25, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Discloses semantic dedup with cosine similarity threshold and instructs to check 'deduplicated' field in response. No annotations provided, so description carries full burden; missing some side effects but sufficient.

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 sentences, no wasted words, front-loaded with purpose. Every sentence adds value.

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, but description mentions checking 'deduplicated' field. Simple two-parameter tool; covers creation and dedup. Could mention async behavior or limits, but adequate.

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 coverage is 100%, so baseline is 3. Description adds an example for linear_issue and slightly rephrases text parameter, but does not significantly enrich beyond 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?

Clearly states the tool creates an open thread to track unresolved work across sessions, distinguishing it from sibling tools like resolve_thread and cleanup_threads.

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?

Provides context for when to use the tool (track unresolved work across sessions) and describes dedup behavior, but does not explicitly state when not to use or compare with alternatives.

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