Skip to main content
Glama

Start a conversation

thread_create
Idempotent

Starts a new conversation with the Barmaan team (support or sales), optionally about one of your orders (subject kind order + order number), projects (kind project + code) or service requests (kind serviceRequest + RQ-… ref). Without confirm:true it only returns a preview and sends nothing; call again with confirm:true only after the human clearly asked you to. A conversation about the same order/project/request already open is reused. Limits: 3 open conversations still waiting for the team, a few new ones per hour.

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": {
      "title": "<title>",
      "body": "<body>"
    },
    "name": "thread_create"
  }
}

Input Schema

NameRequiredDescriptionDefault
bodyYesPlain text only (no HTML), 1-5000 characters.
queueNosupport
titleYes
confirmNofalse = preview only, nothing is sent. true = really send/apply after the human agreed.
subjectNo
client_msg_idNoOptional idempotency key (8-64 letters/digits/-/_). Retrying with the same key never sends twice.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.4/5.0
Behavior5/5

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

Annotations already declare readOnlyHint=false and idempotentHint=true, but the description adds material context beyond them: the two-phase preview-then-send flow, the human-approval prerequisite, reuse of an existing conversation on the same subject, and concrete quotas (3 open conversations, a few per hour). That is behavior an agent could not derive from the structured fields alone.

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 safest constraint (preview unless confirm:true) is front-loaded and every sentence carries information about sending, reuse, or limits. It is dense and slightly list-like in one paragraph, but no sentence is filler.

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 write tool with no output schema, the description covers the approval flow, subject scoping, deduplication, and quotas. It does not say what the preview response contains or what specifically happens when a limit is hit, which is the remaining gap.

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 coverage is 50%, and the description compensates well by mapping subject kinds to their refs (order number, project code, 'RQ-… ref') and explaining the confirm gate. The queue parameter is only hinted at via 'support or sales', and title gets no guidance, but the semantically risky parameters are covered.

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

Purpose4/5

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

The description opens with a specific verb and resource ('Starts a new conversation with the Barmaan team') and scopes it to three optional subject types (order/project/serviceRequest). It clearly reads as a creation tool distinct from retrieval siblings, but it never names an alternative (e.g. thread_close, request_create) to sharpen the boundary.

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?

Explicit when-to-use and when-not-to-use: 'Without confirm:true it only returns a preview and sends nothing; call again with confirm:true only after the human clearly asked you to.' It also states reuse behavior for already-open conversations and the rate/volume limits, leaving little to infer.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources