Skip to main content
Glama

Set Where You Live and Apply

set_markets
Idempotent

Save your home market and application markets to set date and pay-currency display and to answer work-permit questions per country.

Instructions

Save where the user lives and applies. home (a market key, "UK" not "GB") sets the date format and, while home_currency is unset, the currency pay is shown in. apply_in is every market the user applies in, each asking its own work-permit answers; [] reads as home alone, and a market dropped from it keeps its stored answers. home alone leaves apply_in as stored (before any country is chosen, it applies where the user lives). home_currency is ISO 4217; "" follows home again. Only the fields passed change, all in one save: a refused field (an unknown currency) writes none of them. No field passed reads the current values. Returns {home, apply_in, home_currency (the resolved one), setup}: setup is setup status's form-answer readiness, null when that read fails.

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": "set_markets"
  }
}

Input Schema

NameRequiredDescriptionDefault
homeNo
apply_inNo
home_currencyNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv0.14.0
    • changedInput schema / properties / apply_in / anyOf
      Previous value: -[
      -  {
      -    "items": {
      -      "enum": [
      -        "US",
      -        "UK",
      -        "CA",
      -        "AU",
      -        "IE",
      -        "IN",
      -        "DE",
      -        "NL"
      -      ],
      -      "type": "string"
      -    },
      -    "type": "array"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]New value: +[
      +  {
      +    "items": {
      +      "enum": [
      +        "US",
      +        "UK",
      +        "CA",
      +        "AU",
      +        "IE",
      +        "IN",
      +        "DE",
      +        "NL",
      +        "AE"
      +      ],
      +      "type": "string"
      +    },
      +    "type": "array"
      +  },
      +  {
      +    "type": "null"
      +  }
      +]
    • changedInput schema / properties / home / anyOf
      Previous value: -[
      -  {
      -    "enum": [
      -      "US",
      -      "UK",
      -      "CA",
      -      "AU",
      -      "IE",
      -      "IN",
      -      "DE",
      -      "NL"
      -    ],
      -    "type": "string"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]New value: +[
      +  {
      +    "enum": [
      +      "US",
      +      "UK",
      +      "CA",
      +      "AU",
      +      "IE",
      +      "IN",
      +      "DE",
      +      "NL",
      +      "AE"
      +    ],
      +    "type": "string"
      +  },
      +  {
      +    "type": "null"
      +  }
      +]
  2. Addedv0.12.0

TDQS

A4.1/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, idempotentHint=true, destructiveHint=false, and openWorldHint=false, and nothing here contradicts them. The description adds genuinely non-obvious behavior beyond the annotations: writes are atomic ('a refused field ... writes none of them'), omission preserves stored answers, and the call doubles as a read when no field is passed. However, it does not cover permission/auth requirements or what 'refused' means operationally (validation error shape), which limits it to a solid 3 rather than higher.

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?

Every clause carries information — there is essentially no filler, and the purpose statement is front-loaded before the field-by-field rules. The weakness is scanability: the middle section is one dense run-on covering three fields without line breaks or bullets, which makes it easy to miss a rule such as the [] shorthand or the atomic-write guarantee.

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?

There is no output schema, and the description compensates by describing the return object field by field, including what home_currency resolves to and the null-on-failure behavior of setup. Combined with the partial-update and atomicity rules, an agent has everything needed to call this correctly and interpret the response.

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?

Schema description coverage is 0%, so the description must carry the full burden and it does: home is flagged as a market key with the concrete gotcha "UK" not "GB", apply_in is defined as the full application set where [] means home alone and omissions preserve stored answers, and home_currency is constrained to ISO 4217 with "" resetting to follow home. Each parameter gains meaning that the bare schema (two enums and a free string) does not supply.

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 description opens with a specific verb and resource: 'Save where the user lives and applies,' and immediately names the three concrete fields (home, apply_in, home_currency). That is far more specific than the title alone, but it never differentiates itself from sibling setters like set_persona or set_job_preferences, so an agent must infer the boundary from field names rather than being told.

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?

Usage context is unusually well specified for a setter: partial-update semantics ('Only the fields passed change'), a read path ('No field passed reads the current values'), and the important interaction rule that home alone leaves apply_in as stored. What is missing is any explicit routing advice toward alternatives (e.g., a read-only getter) or statement of preconditions; the agent must infer those.

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

Deploy Server

Other Tools