Skip to main content
Glama

set_preferences

Configure session preferences for the Nexus-MCP server to control execution mode, model selection, retry behavior, and output limits for subsequent AI agent calls.

Instructions

Set session-scoped preferences that apply to subsequent prompt/batch_prompt calls.

Preferences persist for the duration of the MCP session. 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

Args: execution_mode: Default execution mode for this session ('default' or 'yolo'). None retains the current session value (use clear_execution_mode=True to reset). model: Default model name for this session (e.g. 'gemini-2.5-flash'). None retains the current session value (use clear_model=True to reset). max_retries: Default max retry attempts for transient errors. None retains the current session value (use clear_max_retries=True to reset). output_limit: Default max output bytes per response. None retains the current session value (use clear_output_limit=True to reset). timeout: Default subprocess timeout in seconds. None retains the current session value (use clear_timeout=True to reset). retry_base_delay: Default base delay seconds for exponential backoff. None retains the current session value (use clear_retry_base_delay=True to reset). retry_max_delay: Default max delay cap seconds for exponential backoff. None retains the current session value (use clear_retry_max_delay=True to reset). clear_execution_mode: If True, resets execution_mode to None regardless of the execution_mode argument. clear_model: If True, resets model to None regardless of the model argument. clear_max_retries: If True, resets max_retries to None regardless of the argument. clear_output_limit: If True, resets output_limit to None regardless of the argument. clear_timeout: If True, resets timeout to None regardless of the argument. clear_retry_base_delay: If True, resets retry_base_delay to None. clear_retry_max_delay: If True, resets retry_max_delay to None. ctx: MCP context (auto-injected by FastMCP).

Returns: Confirmation string with the active preferences as JSON.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
execution_modeNo
modelNo
max_retriesNo
output_limitNo
timeoutNo
retry_base_delayNo
retry_max_delayNo
clear_execution_modeNo
clear_modelNo
clear_max_retriesNo
clear_output_limitNo
clear_timeoutNo
clear_retry_base_delayNo
clear_retry_max_delayNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior4/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It effectively explains key behavioral traits: preferences are session-scoped and persist for the duration of the MCP session, the tool can be called repeatedly to update values, and the relationship between None values and clear_* flags. However, it doesn't mention error conditions or validation rules.

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?

The description is well-structured with clear sections: purpose statement, usage guidelines, parameter explanations, and return value. While comprehensive, it's appropriately sized for a tool with 14 parameters. The front-loaded purpose statement is effective, though the parameter section is lengthy but necessary.

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?

Given the tool's complexity (14 parameters, 0% schema coverage, no annotations), the description provides complete context. It explains the tool's purpose, usage patterns, all parameter semantics, and the return format. With an output schema present, the description doesn't need to detail return values, and it adequately covers all other aspects.

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

Parameters5/5

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

With 0% schema description coverage and 14 parameters, the description compensates fully by providing detailed explanations for every parameter. Each parameter gets a clear description of its purpose, acceptable values, and the relationship between None values and corresponding clear_* flags. The Args section adds significant value beyond the bare schema.

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 tool's purpose with specific verb ('Set') and resource ('session-scoped preferences'), and distinguishes it from sibling tools by mentioning clear_preferences. It explains that preferences apply to subsequent prompt/batch_prompt calls, which differentiates it from get_preferences.

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?

The description provides explicit guidance on when to use this tool vs alternatives: 'Call again to update, or use clear_preferences to reset all fields at once.' It also explains how to clear individual fields vs using clear_preferences for bulk reset, giving clear context for choosing between tools.

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