Skip to main content
Glama

update_settings

update_settings
DestructiveIdempotent

Update the connected TalkJS test app's settings. Supply one or more fields. Custom fields merge; a null entry deletes that field, and custom: null clears all custom fields. Requiring authentication needs backend-generated user tokens; making it optional permits impersonation.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "update_settings"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNoApp name; trimmed and must not be empty.
customNoCustom fields to merge. Values are strings or null to delete; null for the whole field clears all custom fields.
defaultLocaleNoLocale, for example en-US or pl; normalized by TalkJS.
authenticationNoWhether users must supply backend-generated authentication tokens.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already flag destructiveHint=true and idempotentHint=true, so the description's job is lighter. It still adds real value by explaining the merge semantics, the null-to-delete behavior, and the security consequence of the 'optional' authentication mode (impersonation), which justifies the destructive flag. It could still say what precisely is lost on a full custom wipe or whether updates are reversible.

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?

Four short sentences, front-loaded with purpose and then the risky semantics; nothing is padding. A couple of phrasings are slightly compressed ('Requiring authentication needs backend-generated user tokens'), but the structure is easy to parse.

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 destructive, idempotent partial-update tool with no output schema, the description covers the mutation semantics, the deletion path, and the security tradeoff of the authentication enum. Missing only confirmation of auth scope for calling the tool and any indication of what a successful response contains.

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

Parameters4/5

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

Schema coverage is 100%, so the baseline is 3. The description goes beyond the schema by spelling out the merge/null-delete semantics and by stating the operational consequence of each authentication enum value (backend tokens required vs. impersonation permitted), which the schema does not convey.

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 description opens with a specific verb and resource ('Update the connected TalkJS test app's settings'), which cleanly separates it from the read-only sibling get_settings. It does not explicitly name that sibling as a counterpart, so it falls just short of full sibling differentiation.

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?

'Supply one or more fields' implies a partial-patch usage pattern, which is useful guidance. However, there is no explicit statement of when to prefer this tool over get_settings or the secret-key tools, and no prerequisites or when-not-to-use conditions.

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