Skip to main content
Glama
AceDataCloud

AiChat MCP Server

Official
by AceDataCloud

aichat_create_conversation_v2

Manage AI conversations: chat, retrieve, update, delete, and batch operations with model selection, state control, pagination, and async callbacks via the AiChat v2 endpoint.

Instructions

Create/manage conversations via AiChat v2 endpoint.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idNoConversation ID. Required for retrieve/update/delete actions.
asyncNoWhether to process the request asynchronously.
limitNoPagination limit for retrieve_batch.
modelNoModel to use for the request.gpt-4.1
titleNoConversation title.
actionNoOperation to perform: chat (default), retrieve, retrieve_batch, update, or delete.chat
offsetNoPagination offset for retrieve_batch.
presetNoOptional preset model configuration.
messageNoMessage payload as a string or structured content array.
user_idNoFilter or associate by user ID.
messagesNoConversation messages for update/action workflows.
questionNoQuestion text for chat action.
statefulNoWhether to use stateful conversation mode.
max_turnsNoMaximum number of turns for conversation history.
referencesNoOptional list of reference sources.
model_groupNoProvider group filter for retrieve_batch.
callback_urlNoWebhook URL to receive async completion callbacks.
tool_resultsNoTool call results for follow-up turns.
allowed_skillsNoOptional list of skills the agent may use.
application_idNoFilter or associate by application ID.
unattended_policyNoOptional unattended-execution policy configuration.
allowed_mcp_serversNoOptional list of MCP servers the agent may use.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Install Server

TDQS

C2.3/5.0
Behavior2/5

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

With no annotations, the description carries the full burden of disclosing behavior, but it only names the endpoint. It does not mention that the tool can mutate, retrieve, delete, or run asynchronous chat workflows, nor does it describe side effects or prerequisites.

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

Conciseness2/5

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

The description is short and front-loaded, but it is under-specified rather than appropriately concise. A single generic sentence is not enough for a 22-parameter, multi-action tool.

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

Completeness1/5

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

Given the high complexity—22 parameters, five action modes, and no annotations—the description is severely incomplete. It does not explain how actions map to parameters, when each action is appropriate, or what the tool actually returns, leaving the agent to infer almost everything from the schema.

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%, and the schema already documents each parameter, so the baseline is 3. The description itself adds no parameter-level semantics beyond what the schema provides.

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 states a verb and resource ('Create/manage conversations via AiChat v2 endpoint'), so the general domain is clear. However, 'manage' is vague and does not reveal that the tool actually supports five distinct operations (chat, retrieve, retrieve_batch, update, delete). It also does not distinguish this v2 tool from the sibling aichat_create_conversation.

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 guidance on when to use this tool versus aichat_create_conversation or the other siblings. No when-to-use, when-not-to-use, or alternative selection guidance is provided.

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

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/AceDataCloud/AiChatMCP'

If you have feedback or need assistance with the MCP directory API, please join our Discord server