Skip to main content
Glama

Update your job preferences

update_preferences
Idempotent

Change the caller's job preferences: job types, experience levels, remote work, categories, minimum salary, relocation and starting availability. Only the fields given change; every other preference is kept. preferred_salary_min_usd is a yearly figure of at least 10000; null removes the minimum altogether.

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
preferred_remoteNo
preferred_job_typesNo
willing_to_relocateNo
preferred_categoriesNo
preferred_experienceNo
can_start_immediatelyNo
preferred_salary_min_usdNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / preferred_salary_min_usd / anyOf
      Previous value: -[
      -  {
      -    "minimum": 0,
      -    "type": "integer"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]New value: +[
      +  {
      +    "maximum": 500000,
      +    "minimum": 10000,
      +    "type": "integer"
      +  },
      +  {
      +    "type": "null"
      +  }
      +]
  2. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Beyond the mutation, idempotency, and non-destructive annotations, the description discloses patch behavior and explains that a null salary removes the existing minimum. It does not cover empty updates, list replacement behavior, or downstream effects, so it is informative rather than exhaustive.

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?

Three compact sentences front-load the action and scope, then address partial updates and the one special parameter case. The field list is lengthy but directly mirrors the inputs, with no filler.

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 seven-parameter optional update with no output schema, this supplies enough information for most correct invocations. Ambiguity around null and empty-array handling, list replacement, and calls containing no fields prevents full completeness.

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

Parameters4/5

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

With 0% schema description coverage, the description usefully covers all seven inputs and adds yearly salary units plus the non-obvious null-clears-the-minimum rule. It leaves null semantics for the other nullable fields and whether arrays replace or extend existing lists unspecified.

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

Purpose4/5

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

The opening sentence gives a specific verb and resource—changing the caller's job preferences—and enumerates the preference categories involved. This implicitly distinguishes it from update_profile, but no explicit sibling boundary is stated.

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 use case is clear, and 'Only the fields given change' tells an agent it can perform a partial update without supplying every preference. There is no explicit when-not guidance or direction to use update_profile for non-preference profile data.

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