Skip to main content
Glama

Set Session Preferences

set_preferences
Idempotent

Configure default settings for execution mode, model, retries, timeouts, and other parameters to apply to all subsequent prompt calls until explicitly cleared.

Instructions

Set persistent preferences that apply to subsequent prompt/batch_prompt calls.

Preferences persist across MCP sessions. Call again to update, or use clear_preferences to reset all fields at once.

To clear a single field while keeping others, pass the corresponding clear_* flag: set_preferences(clear_model=True) # clears model, keeps execution_mode

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
execution_modeNoDefault execution mode ('default' or 'yolo'). None retains the current value (use clear_execution_mode=True to reset).
modelNoDefault model name (e.g. 'gpt-5.2'). None retains the current value (use clear_model=True to reset).
max_retriesNoDefault max retry attempts for transient errors. None retains the current value (use clear_max_retries=True to reset).
output_limitNoDefault max output bytes per response. None retains the current value (use clear_output_limit=True to reset).
timeoutNoDefault subprocess timeout in seconds. None retains the current value (use clear_timeout=True to reset).
retry_base_delayNoDefault base delay seconds for exponential backoff. None retains the current value (use clear_retry_base_delay=True to reset).
retry_max_delayNoDefault max delay cap seconds for exponential backoff. None retains the current value (use clear_retry_max_delay=True to reset).
elicitNo
confirm_yoloNo
confirm_vague_promptNo
confirm_high_retriesNo
confirm_large_batchNo
clear_execution_modeNoIf True, resets execution_mode to None regardless of the execution_mode argument.
clear_modelNoIf True, resets model to None regardless of the model argument.
clear_max_retriesNoIf True, resets max_retries to None regardless of the argument.
clear_output_limitNoIf True, resets output_limit to None regardless of the argument.
clear_timeoutNoIf True, resets timeout to None regardless of the argument.
clear_retry_base_delayNoIf True, resets retry_base_delay to None.
clear_retry_max_delayNoIf True, resets retry_max_delay to None.
clear_elicitNo
clear_confirm_yoloNo
clear_confirm_vague_promptNo
clear_confirm_high_retriesNo
clear_confirm_large_batchNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior4/5

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

Annotations already indicate idempotency ('idempotentHint': true) and non-destructiveness. The description adds value by explaining persistence across sessions and the update semantics. No contradictions found.

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

Conciseness5/5

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

Well-structured with three concise paragraphs: purpose, persistence, and example usage. No unnecessary words, every sentence adds value.

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

Completeness5/5

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

For a tool with 24 parameters (none required) and an output schema, the description covers the key behavioral aspects: persistence, update, clearing, and relation to sibling tools. The output schema handles return values, so no further detail needed.

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 58% with descriptions for most fields. The description explains the overall pattern of using 'None' to retain values and 'clear_*' flags to reset, which adds context beyond individual parameter descriptions but does not detail every parameter.

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

Purpose5/5

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

The description clearly states the verb ('Set'), resource ('persistent preferences'), and scope ('apply to subsequent prompt/batch_prompt calls'). It effectively distinguishes from sibling tool 'clear_preferences' by mentioning its specific function.

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

Usage Guidelines5/5

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

Provides explicit guidance on when to use (set preferences for future calls), persistence across sessions, update behavior, and how to clear fields individually using 'clear_*' flags. Also names 'clear_preferences' as alternative for resetting all fields.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/j7an/nexus-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server