SingChat

Set up SingChat

singchat_setup

Get the user up and running with SingChat live-chat. Call this FIRST. If no authenticated workspace is configured, this creates a brand-new free workspace and returns a short-lived, single-use browser claim link plus the website embed snippet. The user chooses their own sign-in details in the browser; no reusable credentials are returned to the model. If a workspace is already authenticated, it returns THIS workspace's embed snippet and dashboard link (it never creates a duplicate workspace).

Input Schema

TableJSON Schema

Name	Required	Description	Default
`name`	No	Optional workspace/brand name for a newly created workspace. Ignored if a key is already set.

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

First observedJul 16, 2026

TDQS

A4.3/5.0

Behavior4/5

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

No annotations, so description carries full burden. Discloses workspace creation, short-lived claim link, embed snippet, dashboard link, and that no reusable credentials are returned. Does not cover error scenarios or rate limits, but for a setup tool the key behaviors are well-explained.

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?

Description is a single paragraph with three sentences. It front-loads the main purpose, then explains two cases. Efficient, no unnecessary information, though slightly long for a simple tool.

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?

Without an output schema, the description adequately describes return values (claim link, embed snippet, dashboard link) and side effects. Doesn't detail exact formats, but the agent can infer what to do with the results. Sufficient for a setup tool.

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 100% but description adds value by explaining that 'name' is ignored when workspace already exists. This clarifies conditional behavior beyond the schema's basic description.

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?

Clear verb 'Set up' and resource 'SingChat live-chat'. Distinguishes from siblings by stating 'Call this FIRST' and explaining the two distinct behaviors (new vs existing workspace). No ambiguity about what the tool accomplishes.

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?

Explicitly marks this as the first call to make, and describes when to use based on authentication state. Does not explicitly mention alternatives, but the context provided (new vs existing) guides appropriate use versus other tools like get_embed_snippet or claim_account.

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

All SingChat tools Inspect

Try in Browser

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.1/5.0

Disambiguation4/5

Tools are largely distinct, with clear purposes for knowledge management, conversations, FAQs, and setup. The only potential overlap is between 'search' (general help) and 'search_knowledge' (workspace KB), but descriptions clarify the context.

Naming Consistency5/5

All tool names follow a consistent verb_noun pattern in snake_case (e.g., add_knowledge, list_conversations, manage_faq). No mixing of conventions or vague verbs.

Tool Count5/5

17 tools is well-scoped for a live-chat and AI agent workspace server. The set covers setup, knowledge base, conversations, FAQs, analytics, keywords, and embedding without being overwhelming.

Completeness4/5

The tool surface is comprehensive for core workspace management and support: setup, knowledge ingestion/search, conversation handling, FAQs, analytics, and keywords. Minor gaps like user management or advanced channel configuration, but nothing that critically hinders agent workflows.

Resources

Need Help?