CometChat

Official

by cometchat

Overview Schema Source Related Servers Discussions Admin

TypeScript

Remote

Get CometChat Implementation Bundle

get_cometchat_implementation_bundle

Read-only

Retrieve a curated implementation bundle for a named CometChat integration scenario, with prerequisites, install commands, configuration, code examples, and common pitfalls for major platforms.

Instructions

Returns a curated implementation bundle for a named CometChat integration scenario. Each bundle includes prerequisites, install commands, configuration, working code examples, and common pitfalls. Available bundles cover common integration patterns across React, Flutter, iOS, Android, React Native, and the JavaScript SDK.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`bundle`	Yes	Bundle name in lowercase kebab-case, e.g. 'react-uikit-quickstart'.

Output Schema

TableJSON Schema

Name	Required	Description
`title`	Yes	Human-readable bundle title.
`bundle`	Yes	Bundle identifier.
`content`	Yes	The full implementation recipe as markdown.
`framework`	Yes	Target framework/platform.
`last_verified`	Yes	Date the bundle was last verified against live SDK versions.
`prerequisites`	Yes	Prerequisites before applying the bundle.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedv0.1.6Sep 22, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "additionalProperties": false,
+  "properties": {
+    "bundle": {
+      "description": "Bundle identifier.",
+      "type": "string"
+    },
+    "content": {
+      "description": "The full implementation recipe as markdown.",
+      "type": "string"
+    },
+    "framework": {
+      "description": "Target framework/platform.",
+      "type": "string"
+    },
+    "last_verified": {
+      "description": "Date the bundle was last verified against live SDK versions.",
+      "type": "string"
+    },
+    "prerequisites": {
+      "description": "Prerequisites before applying the bundle.",
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    "title": {
+      "description": "Human-readable bundle title.",
+      "type": "string"
+    }
+  },
+  "required": [
+    "bundle",
+    "title",
+    "framework",
+    "prerequisites",
+    "last_verified",
+    "content"
+  ],
+  "type": "object"
+}

First observedv0.1.5Jul 15, 2026

TDQS

A4/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true, so no contradiction exists. The description adds genuine behavioral context by specifying that the result includes prerequisites, install commands, configuration, working code examples, and common pitfalls, which tells the agent what to expect from the tool beyond the read-only guarantee.

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 compact sentences front-load the core action and resource, then efficiently summarize bundle contents and supported platforms. Every sentence adds value and there is no redundant restatement of the title or schema.

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 single-parameter read-only tool with an output schema, the description is nearly complete: it explains what the bundle contains and which platforms are covered. It falls just short by not explicitly pointing the agent to list_cometchat_bundles for discovering available bundle names, though the sibling tool name makes this inferable.

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 parameter description already documents the kebab-case format and gives an example. The tool description adds little beyond saying the bundle is for a named integration scenario, so the schema carries the semantic weight.

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 uses a specific verb ('Returns') tied to a clear resource ('a curated implementation bundle') and a named integration scenario. It also enumerates what the bundle contains, distinguishing this tool from documentation search or bundle listing siblings.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The intended use is implied: call this when you need a ready-made implementation bundle for a CometChat scenario. However, there is no explicit guidance on when to use it versus list_cometchat_bundles or fetch_cometchat_doc_page, and it does not mention that list_cometchat_bundles should be used first to discover valid bundle names.

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

Deploy Server