Skip to main content
Glama

Update personalization settings

spur_update_personalization_settings
Destructive

Set voice, goal, approved angles, fallbacks, custom AI fields and human review. Read the catalog first. Enabling auto_generate can spend Actions on subsequent list additions; confirm the settings with the user.

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": {
      "settings": "<settings>",
      "confirm": "<confirm>"
    },
    "name": "spur_update_personalization_settings"
  }
}

Input Schema

NameRequiredDescriptionDefault
confirmYesSet to true ONLY after the user explicitly approved this exact action in the conversation. Never assume approval.
settingsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.6/5.0
Behavior4/5

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

Adds real context beyond annotations: enabling auto_generate can spend Actions on later list additions, and the settings must be user-confirmed. Given destructiveHint=true and openWorldHint=true, this cost/approval disclosure is meaningful. It stops short of saying whether the update replaces the whole settings object or merges with existing values, which matters for a destructive write.

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 operation and followed by the prerequisite and the cost caveat. Every sentence carries information; minor ambiguity (which catalog) rather than padding.

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 destructive, non-idempotent mutation with no output schema and nested parameters, the definition covers approval and cost but omits replace-vs-merge semantics and what happens to omitted fields, which an agent needs to call it safely.

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?

The description maps several top-level settings keys to human terms (voice/tone, goal, approved angles, fallbacks, custom AI fields, human review) and calls out auto_generate specifically. With 50% schema coverage and deeply nested objects (custom_fields conditions, max_chars, fallback), it leaves meaningful semantics to the schema, so this is a baseline-plus result.

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?

States a specific verb (Set) plus the resource and enumerates the settings areas: tone/voice, goal, approved angles, fallbacks, custom AI fields, human review. An agent can distinguish this from the read-oriented siblings (spur_get_personalization) and the generation sibling, though no sibling is named explicitly.

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?

Provides a sequencing rule ("Read the catalog first") and an approval rule ("confirm the settings with the user"), which is useful context. However, the catalog tool is never named, and there is no explicit statement of when to use this versus spur_generate_personalization or spur_get_personalization.

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