Skip to main content
Glama

set_user_preference

Saves a persistent developer preference or global coding rule, such as a test runner or naming convention, so AI coding agents retain conventions across sessions.

Instructions

Save a persistent developer preference or global coding rule (e.g., preferred test runner, naming conventions, forbidden packages).

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": {
      "key": "<key>",
      "value": "<value>"
    },
    "name": "set_user_preference"
  }
}

Input Schema

NameRequiredDescriptionDefault
keyYesUnique preference key (e.g. 'typescript.strict_mode', 'db.orm_policy').
valueYesPreference rule or value.
categoryNoPreference category (e.g. 'coding-style', 'stack', 'security').

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.3.0

TDQS

B3.4/5.0
Behavior3/5

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

With no annotations, the description carries the full behavioral burden; it usefully discloses durability ('persistent'), which is real context beyond the schema. However, it omits critical setter semantics: whether saving an existing key overwrites or errors, whether changes are reversible, and what the response contains, leaving an agent unsure of upsert behavior.

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?

A single, front-loaded sentence with the verb first and parenthetical examples that earn their place by illustrating the resource. No redundant or filler wording.

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 three-parameter mutation tool with no annotations and no output schema, the definition covers what is saved but not enough of the surrounding behavior. Overwrite semantics and failure modes are the main gaps an agent would need before calling it confidently.

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 coverage is 100%, so all three parameters are already documented in the schema, setting the baseline at 3. The examples in the description ('preferred test runner', 'forbidden packages') add a sense of what belongs in the value field but do not clarify key formatting or category usage beyond what the schema states.

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 ('Save') and resource ('persistent developer preference or global coding rule') and grounds it with concrete examples (test runner, naming conventions, forbidden packages). It contrasts implicitly with the get/list-style sibling get_user_preferences, though it does not explicitly distinguish itself from write-adjacent siblings like remember_decision or sync_workspace_rules.

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?

The word 'persistent' and 'global coding rule' imply the scope of use (durable, cross-session rules rather than session-local facts), but there is no explicit when-to-use or when-not-to-use guidance, and no named alternative such as remember_decision for one-off decisions versus durable rules.

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