Skip to main content
Glama

CometChat Docs

by io.github.cometchat

Search CometChat Documentation

search_cometchat_docs
Read-only

Searches CometChat documentation including SDK guides (JavaScript, React, iOS, Android, Flutter, React Native), UI Kit references, REST API documentation, integration tutorials, and OpenAPI specs. Returns ranked snippets with titles and direct links to source pages. Supports an optional version filter to scope results to a specific documentation version.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoMaximum number of results to return. Default 10, maximum 25.
queryYesSearch query. 1–500 characters.
versionNoOptional documentation version filter, e.g. 'v4' or 'v3'.

TDQS

A4/5.0
Behavior4/5

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

Annotations provide readOnlyHint=true. Description adds that the tool returns ranked snippets with titles and direct links, which is valuable behavioral context beyond the annotation. No contradictions.

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?

Three sentences with no redundancy: first sentence states purpose and scope, second describes output, third mentions optional filter. Every sentence adds value.

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 simple search tool with 3 parameters and no output schema, the description adequately covers what is searched, output format, and optional version filter. It is complete enough for an agent to understand its use.

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%, so the description does not need to repeat parameter details. It adds minor value by highlighting the version filter's purpose. Baseline 3 is appropriate.

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?

Description uses specific verb 'searches' and clearly lists the scope of documentation (SDK guides, UI Kit, REST API, etc.). It distinguishes itself from siblings (fetch_cometchat_doc_page and get_cometchat_implementation_bundle) by being a search tool.

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?

Description implies usage for searching documentation but does not explicitly state when to use this tool instead of siblings or mention prerequisites or exclusions. Guidance is minimal.

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

All CometChat Docs toolsInspect
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.2/5.0
Disambiguation5/5

Each tool has a clearly distinct purpose: fetching a specific page, getting a curated implementation bundle, and searching across docs. No overlap in functionality.

Naming Consistency5/5

All tool names follow a consistent verb_cometchat_noun pattern (e.g., fetch_cometchat_doc_page, get_cometchat_implementation_bundle), making them predictable and easy to distinguish.

Tool Count5/5

With 3 tools, the server is well-scoped for its purpose of accessing CometChat documentation. Each tool serves a distinct need without being too few or too many.

Completeness4/5

The core operations of fetching a page and searching are covered. The addition of implementation bundles adds value, but a tool to list available bundles or sections is missing, which agents might need for discovery.

Resources