Skip to main content
Glama

Replace a preference set

update_preferences
Idempotent

Replace one of YOUR preference sets (requires api:account). kind=market_brief takes market_brief; kind=trade_routing takes trade_routing. Each REPLACES THE WHOLE SET: a field you leave out goes back to its default. So call get_preferences with the same kind first, change only what the user asked for, and send the whole set back. The response echoes what was stored. market_brief: hidden_rows ({category: [row ids]}, categories global | crypto | fx | commodities | sectors | bonds, ≤64 ids each), crypto_rows (3-12), display ({timeframe: 1d | 5d | 1m | 3m | ytd | 1y, view: list | bars | lines, layout: grid | full}), opportunity_hidden_subjects (asset:… subject ids, ≤256), opportunity_hidden_asset_classes (equity | crypto | commodity | fx | index | prediction) and opportunity_hyperliquid_only. Set advisory_timeframe_only=true to update just advisory_timeframe without replacing brief settings. Omitting advisory_timeframe preserves it; explicitly including it in a normal full-set write updates it. advisory_timeframe (ltf | mtf | htf, or null to follow the quiz) highlights one suggestion while keeping all alternatives visible; it does not change automated holding rules. trade_routing: default_destination (hyperliquid | brokerage) and symbol_overrides ({TICKER: hyperliquid | brokerage}, ≤200, US tickers only) — it preselects the trade ticket's destination; it never routes or places an order. The trading profile (risk caps, agent mode, chat execution) cannot be changed here.

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": {
      "kind": "<kind>"
    },
    "name": "update_preferences"
  }
}

Input Schema

NameRequiredDescriptionDefault
kindYes
market_briefNoREQUIRED for kind=market_brief: the whole set
trade_routingNoREQUIRED for kind=trade_routing: the whole set

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / market_brief / properties / advisory_timeframe
      Added value: +{
      +  "anyOf": [
      +    {
      +      "enum": [
      +        "ltf",
      +        "mtf",
      +        "htf"
      +      ],
      +      "type": "string"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ]
      +}
    • addedInput schema / properties / market_brief / properties / advisory_timeframe_only
      Added value: +{
      +  "type": "boolean"
      +}
  2. Added

TDQS

A4.9/5.0
Behavior5/5

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

The annotations only declare readOnly=false, destructive=false, idempotent=true and openWorld=false; the description goes further by disclosing the whole-set overwrite semantics (omitted fields revert to defaults), the api:account auth requirement, that the response echoes what was stored, and that trade_routing "never routes or places an order." The reset-on-omit behavior is somewhat more consequential than destructiveHint=false suggests, but the description rather than the annotation is the accurate source here, so this is disclosure, not contradiction.

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 critical constraint ("Each REPLACES THE WHOLE SET") is front-loaded and the per-kind field inventory is organized by kind. It is dense and slightly repetitive — the replacement rule is restated in the advisory_timeframe paragraph — but nearly every clause carries operational meaning.

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 nested 3-parameter mutation tool with no output schema, the definition covers the write contract, the read-before-write workflow, per-field ranges and enums, the escape hatch for a single field, and the return behavior. Nothing an agent needs to call it safely is missing.

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?

Beyond the 67%-covered schema it adds real meaning: null for advisory_timeframe means "follow the quiz," ltf/mtf/htf only highlights a suggestion without changing holding rules, hidden_rows categories and the ≤64 cap, crypto_rows 3-12, and that symbol_overrides are US tickers only (≤200). It also explains advisory_timeframe_only as the narrow single-field path, which the schema only names.

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?

"Replace one of YOUR preference sets" gives a specific verb (replace) and resource (preference set), and the two kind values split the tool into clearly named subject areas. The sibling get_preferences is named as the read counterpart, so an agent can distinguish read from write without inspecting either schema.

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?

Explicit procedure: call get_preferences with the same kind first, change only what the user asked for, and send the whole set back. It also gives the negative case — "The trading profile (risk caps, agent mode, chat execution) cannot be changed here" — and explains the omit-vs-include behavior for advisory_timeframe.

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