HAL

import_conversation

Import a single historical conversation silently (no webhooks, no notifications). Use for migrating data from other chat platforms.

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": {
      "visitor": "<visitor>",
      "messages": "<messages>"
    },
    "name": "import_conversation"
  }
}

Input Schema

Name	Required	Description
`visitor`	Yes	Visitor info — matched by email first, then user_id, then external_id, or creates new
`messages`	Yes	Messages to import (1-1000, ordered chronologically)
`project_id`	No	Target project ID
`conversation`	No	Conversation metadata (defaults to resolved status)
`project_slug`	No	Target project slug (helpdesk slug)

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 30, 2026

TDQS

A3.7/5.0

Behavior3/5

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

With no annotations, the description carries the full burden, and it does disclose the most important behavioral trait: the import is silent (no webhooks, no notifications). It says nothing about duplicate handling, whether automations or matching side effects fire, permissions, or what is returned, leaving significant gaps for a mutation tool.

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 tight sentences; the silence/no-side-effects constraint is front-loaded right after the action, and nothing is wasted.

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

Completeness3/5

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

The tool has nested objects and five parameters with no output schema, yet the description never says what comes back (e.g., created conversation ID) or how partial failures behave. The schema covers inputs well, but the return contract is entirely undocumented.

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%, including nested visitor matching order and message field semantics, so the schema does the heavy lifting. The description adds no parameter-level meaning beyond it, making the baseline 3 appropriate.

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?

States a specific verb and resource (import a single historical conversation) and the word 'single' implicitly separates it from the sibling import_conversations bulk tool. It stops short of naming that sibling explicitly, so the contrast must be inferred.

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?

'Use for migrating data from other chat platforms' gives a clear selection context. It does not state when to prefer import_conversations (bulk) over this one, nor any prerequisites such as project scoping, so the guidance is contextual but not exclusionary.

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

All HAL 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?