alpaca-mcp-server

Official

Overview Schema Source Related Servers Discussions Admin

update_account_config

Update Alpaca account settings like trading modes, order blocking, fractional trading, margin, options level, and overnight trading, preserving unspecified fields.

Instructions

Updates one or more account configuration settings. Only the fields you provide will be changed; all others retain their current values.

Input Schema

TableJSON Schema

Name	Required	Description
`no_shorting`	No	If true, account becomes long-only mode.
`suspend_trade`	No	If true, new orders are blocked.
`fractional_trading`	No	If true, account is able to participate in fractional trading
`trade_confirm_email`	No	all or none. If none, emails for order fills are not sent.
`max_margin_multiplier`	No	Can be "1", "2", or "4"
`ptp_no_exception_entry`	No	If set to true then Alpaca will accept orders for PTP symbols with no exception. Default is false.
`disable_overnight_trading`	No	If true, overnight trading is disabled.
`max_options_trading_level`	No	The desired maximum options trading level. 0=disabled, 1=Covered Call/Cash-Secured Put, 2=Long Call/Put, 3=Spreads/Straddles.

Output Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedv2.3.2Sep 18, 2026

removedInput schema / properties / dtbp_check

Removed value: -{
-  "description": "both, entry, or exit. Controls Day Trading Margin Call (DTMC) checks.",
-  "enum": [
-    "both",
-    "entry",
-    "exit"
-  ],
-  "type": "string"
-}

removedInput schema / properties / pdt_check

Removed value: -{
-  "description": "`both`, `entry`, or `exit`. If entry orders will be rejected on entering a position if it could result in PDT being set for the account. exit will reject exiting orders if they would result in PDT being set.",
-  "example": "entry",
-  "type": "string"
-}

removedInput schema / properties / ptp_no_exception_entry / x-stoplight
```
Removed value: -{
-  "id": "8qvrtnzouzp80"
-}
```

Addedv2.0.0Apr 15, 2026

TDQS

A4.2/5.0

Behavior4/5

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

With no annotations provided, the description carries the burden of behavioral disclosure. It communicates that updates are partial (only provided fields change), which is a critical behavior. It does not detail side effects, permissions, or error handling, but the partial update disclosure adds meaningful transparency beyond the basic 'updates' verb.

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?

The description is two concise sentences, front-loaded with the primary action and immediately followed by the key partial-update clarification. Every word earns its place with no waste.

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?

The tool benefits from a rich schema and output schema, so return values do not need elaboration. The description covers the essential update semantics and partial-update behavior. It does not mention prerequisites or postconditions, but for a config update tool this is largely adequate.

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 description coverage is 100%, so the parameters are already well-documented. The description adds little beyond stating the partial-update semantics, which is a general behavior rather than per-parameter detail. Baseline of 3 is appropriate.

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 updates account configuration settings, using the specific verb 'updates' and naming the resource. This distinguishes it from the sibling 'get_account_config' and other config-related tools.

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

Usage Guidelines4/5

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

The description provides clear context on how to use the tool, emphasizing that only provided fields are changed and others are retained. It does not explicitly name alternatives or when-not-to-use conditions, but the partial-update behavior serves as a key usage guideline.

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

Deploy Server