Skip to main content
Glama
Sign In

Chatway Live Chat

by app.chatway.mcp
OverviewDiscussionsAdmin

Search Knowledge Base

search-knowledge-base
Read-onlyIdempotent

Search the authenticated team’s Chatway knowledge-base questions and answers. Use the returned content to answer or draft a response without inventing unsupported information. Use it before drafting a reply with send-message so answers match the team's own content.

Input Schema

NameRequiredDescriptionDefault
limitNoMaximum results to return, from 1 to 50.
queryYesSearch term for knowledge base Q&A.

Output Schema

NameRequiredDescriptionDefault
resultsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / limit / description
      Previous value: -"Maximum results to return."New value: +"Maximum results to return, from 1 to 50."
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "properties": {
+    "results": {
+      "items": {
+        "properties": {
+          "answer": {
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "id": {
+            "type": "integer"
+          },
+          "question": {
+            "type": [
+              "string",
+              "null"
+            ]
+          }
+        },
+        "type": "object"
+      },
+      "type": "array"
+    }
+  },
+  "type": "object"
+}
  2. First observed

TDQS

A3.9/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive, and closed-world, so the safety profile is covered. The description adds a useful grounding constraint (use returned content, don't invent unsupported information) but says nothing about result quality, empty-result behavior, or match semantics. The output schema covers return values.

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?

Three short sentences, front-loaded with the resource and scope, then the usage rule. Slight overlap between 'use the returned content to answer or draft a response' and 'use it before drafting a reply with send-message' but nothing wasteful.

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?

With an output schema present, rich annotations, and full schema coverage, the description only needs to convey purpose and usage, which it does. The one gap is search behavior (matching semantics, behavior on no matches), which would help an agent set expectations.

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 both parameters (query, limit) are already documented in structured data; a 3 is the baseline. The description adds no meaning about how 'query' is matched (keyword vs. semantic) or what happens with an empty query, which would have been genuinely useful.

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?

States a specific verb and resource ('Search the authenticated team's Chatway knowledge-base questions and answers') with a clear scope qualifier (the authenticated team's own content). This is easily distinguished from the sibling search tools (search-contacts, search-conversations), which target different resources.

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?

Gives an explicit trigger ('Use it before drafting a reply with send-message so answers match the team's own content') and names the sibling it pairs with. It lacks an explicit when-not case (e.g., don't use for conversation history — use list-conversation-messages instead), which keeps it from a 5.

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

All Chatway Live Chat toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources