Skip to main content
Glama

Update search preferences

update_preferences
DestructiveIdempotent

Saves the caller's search preferences on their Boardwalk account. Only the fields passed are changed, and each one replaces the previous value on the caller's own row, even when get_preferences returned a teammate's blob. firstRunCompleted=true marks the short first-run complete. Does not use credits.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "update_preferences"
  }
}

Input Schema

NameRequiredDescriptionDefault
notesNo
websiteNo
geographyNo
lookingForNoProject types / ICP phrases.
firstRunCompletedNo
exampleProjectFeedbackNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior5/5

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

Goes well beyond the annotations by explaining that each passed field replaces the prior value (giving concrete meaning to destructiveHint=true), that writes land on the caller's own row even when get_preferences returned a teammate's blob, and that firstRunCompleted=true marks the short first-run complete. These are non-obvious behaviors an agent could not derive from readOnlyHint/destructiveHint/idempotentHint alone.

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?

Four short sentences, front-loaded with the core action, then the overwrite rule, then the special flag, then the cost note. Every sentence carries information; the "teammate's blob" phrasing is slightly cryptic but is doing real work.

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?

For a mutating, nested-object tool with no output schema, it covers write target, overwrite semantics, a special-purpose flag, and credit cost. The remaining gap is the lack of field-level meaning for most parameters, though the schema's maxItems and enum constraints partially compensate.

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 only 17% across 6 parameters, so the description must compensate. It does add partial-update and replacement semantics that apply to every field, and explains firstRunCompleted, but notes, website, geography (city/state/county IDs), and exampleProjectFeedback receive no meaning beyond their schema shape.

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?

States a specific verb ("Saves") plus resource ("search preferences") and scope ("the caller's Boardwalk account"), and implicitly contrasts with the read sibling get_preferences. An agent can distinguish it from the read path without inspecting the schema.

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?

Conveys clear operating context: partial updates ("Only the fields passed are changed"), the relationship to get_preferences, and the cost note "Does not use credits" which helps an agent decide freely whether to call it. It stops short of explicit when-not-to-use conditions or naming an alternative write path.

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