SingChat

Fetch

fetch

Fetch the full text of a single document by id, using an id returned by the search tool. With a workspace API key this reads a knowledge document from that workspace; without a key it reads a SingChat help article. Returns id, title, text, url, and optional metadata.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`id`	Yes	The document id returned by the search tool.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`id`	Yes
`url`	Yes
`text`	Yes
`title`	Yes
`metadata`	No

Schema Changelog

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

First observedJul 16, 2026

TDQS

A4.4/5.0

Behavior4/5

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

Discloses return fields and auth-dependent behavior (workspace vs help article), but no annotations provided; could mention error cases or rate limits.

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 concise sentences with no redundancy, front-loading the core action and then adding essential context.

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?

Adequately covers purpose, input, auth, and output for a simple fetch operation; minor gaps like potential error conditions or scope limitations.

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 covers the single parameter fully; description adds meaningful context about its origin (from search) and behavior based on API key.

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?

The description clearly states it fetches full text of a single document by id from the search tool, distinguishing it from search and other tools.

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 ties usage to a prior search call and explains varying behavior based on API key presence, though does not explicitly exclude alternatives.

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?