Skip to main content
Glama

ui_bind_conversation

Pre-bind a newly launched conversation ID to a task and project so the chat is linked before work begins. Use it to attach new chats to existing project tasks.

Instructions

App-only: pre-bind a newly launched conversationId to a task.

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": {
      "conv_id": "<conv_id>",
      "project_id": "<project_id>"
    },
    "name": "ui_bind_conversation"
  }
}

Input Schema

NameRequiredDescriptionDefault
conv_idYes
task_idNo
project_idYes
workspace_dirNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.4/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full behavioral burden, and it discloses almost nothing: whether the binding is idempotent, whether it mutates or creates state, whether it fails if the conversation is already bound, or what permissions are required are all unstated. Only the implication of a state-changing bind and an app-only constraint are conveyed.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The definition is one short, front-loaded sentence with no filler, which is structurally sound. But the brevity comes at the cost of under-specification, and the 'App-only:' tag consumes one of the few available words without being clarified.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a four-parameter mutation tool with no annotations, no schema descriptions, and no output schema, this single sentence is not sufficient. An agent cannot determine required permissions, idempotency, expected response, or the role of half the parameters from this definition alone.

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

Parameters2/5

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

Schema description coverage is 0% for four parameters, so the description must compensate and does not. It hints at conv_id ('conversationId') and loosely at task_id ('to a task'), but says nothing about project_id, workspace_dir, the nullability of task_id, or when task_id should be omitted versus supplied.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names a specific verb-and-resource pair ('pre-bind a conversationId to a task'), so the general action is discernible. However, 'pre-bind' and 'newly launched' are not explained, and the unexplained 'App-only' prefix adds ambiguity rather than distinguishing this tool from any sibling, none of which appear conversation-related.

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

Usage Guidelines2/5

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

There is no explicit when-to-use guidance, no prerequisites, and no indication of what to do if the conversation is already bound or already has a task. The fragment 'App-only' weakly implies a client/environment restriction but is left for the agent to guess at.

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