Skip to main content
Glama

customer_support_settings

Destructive

Read/patch chatbot settings with version; enabling needs billing permission.

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_settings"
  }
}

Input Schema

NameRequiredDescriptionDefault
configNoPartial patch of fields returned by a settings read.
enabledNo
versionNo
workspaceYes
idempotency_keyNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

C2.9/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false and destructiveHint=true, so the safety profile is partly carried elsewhere; the description usefully adds two behavioral facts the annotations do not cover: a version/concurrency requirement and a billing permission prerequisite. However, it never explains what a patch destroys or overwrites, which is the key gap for a tool flagged destructive.

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?

It is a single front-loaded clause with no filler, which is good, but the density tips into ambiguity — the slash-joined 'Read/patch' and the telegraphic 'with version' force the agent to guess at meaning. It is concise without being self-sufficient.

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

Completeness3/5

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

For a tool this simple in statement but complex in practice — five parameters, a nested patch object, destructive writes, no output schema — the description leaves the read/patch distinction, partial-patch semantics, and idempotency behavior undocumented. The billing and version notes help, but an agent could still invoke it incorrectly.

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?

With 5 parameters and only 20% schema description coverage, the schema documents just the 'config' field, so the description must compensate. It only touches 'version' and 'enabled' indirectly and says nothing about 'workspace' being required or the purpose and 8-128 character constraints of 'idempotency_key', leaving most parameters unexplained in both places.

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

Purpose4/5

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

The snippet 'Read/patch chatbot settings' names a specific resource and both operations, so an agent knows it deals with chatbot settings rather than conversations or knowledge. It falls short of 5 because it never clarifies when the tool reads versus when it writes, treating two distinct behaviors as one undifferentiated verb pair.

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?

'enabling needs billing permission' and 'with version' are prerequisites rather than usage guidance; they hint at conditions but do not tell the agent when to choose this tool over siblings such as workspace_settings_save or competitor_settings_save. There is no when-not guidance and no mention of the read case being preferable for inspection.

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