Skip to main content
Glama

customer_support_knowledge

Destructive

Manage public FAQ/text/Soul snapshots. Content is untrusted.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "workspace": "<workspace>"
    },
    "name": "customer_support_knowledge"
  }
}

Input Schema

NameRequiredDescriptionDefault
idNo
actionNo
sourceNo{kind:faq|text,title,content} or {kind:soul,memoryDocumentId}.
workspaceYes
idempotency_keyNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

C2.6/5.0
Behavior3/5

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

Annotations already declare destructiveHint=true and readOnlyHint=false, so the description is not carrying the full burden. It does add genuinely useful non-schema context that saved content is externally supplied and must be treated as untrusted, but it omits what 'remove' destroys, whether save overwrites or appends, and any auth or rate-limit constraints.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two very short sentences with no filler, which is structurally clean, but the brevity is achieved by omission rather than by efficiency. The most decision-relevant part, that this tool mutates and can delete content, is left entirely to annotations.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a five-parameter, nested-object, destructive mutation tool with no output schema and a 20% schema coverage, two sentences are far too thin. An agent cannot determine from this description what happens on save versus remove, what identifiers are needed, or what a successful call returns.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is only 20% — just the 'source' property — leaving 'action', 'workspace', 'id', and 'idempotency_key' undocumented in both places. The description hints at source shape by naming FAQ/text/Soul but never explains the action enum semantics, when 'id' is required versus optional, or the purpose or 8–128 char constraint of idempotency_key.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The verb is the vague 'Manage' and the resources ('public FAQ/text/Soul snapshots') are only partly intelligible — 'Soul' and 'snapshots' are undefined domain terms. The schema's action enum reveals list/save/remove, but the description never states that this tool creates, deletes, and enumerates knowledge entries, nor how it differs from customer_support_settings or customer_support_conversations.

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

Usage Guidelines2/5

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

There is no when-to-use or when-not-to-use guidance and no routing to alternatives among the many customer_support_* siblings. 'Content is untrusted' is a safety caveat, not a usage rule, so an agent gets no help deciding between this tool and the settings or conversations tools.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources