Skip to main content
Glama

set_client_unit_default

Set the unit system new clients (and clients added without the app) start in: "metric" (kg, cm), "imperial" (lbs, in) or null to follow each phone's region. Does not change units a client already chose. (confirm-gated: previews until confirm: true)

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": {
      "units": "<units>"
    },
    "name": "set_client_unit_default"
  }
}

Input Schema

NameRequiredDescriptionDefault
unitsYes
confirmNoMust be true to actually execute. If false/omitted, returns a preview only.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.4/5.0
Behavior4/5

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

With only readOnlyHint=false in annotations, the description adds important behavior: this is a mutation that is confirm-gated and previews until confirm: true. It also discloses that existing client choices are unaffected, though it does not mention permissions or side effects beyond that.

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 compact sentences with the scope and behavior front-loaded. Every clause adds actionable meaning, including the value meanings and the confirm-gate note.

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 two-parameter mutation tool with no output schema and minimal annotations, the description covers the effect, non-effect, and confirmation flow. It could be slightly more complete by explicitly stating that units is required, but the schema already carries that.

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?

Schema coverage is 50%, and the description compensates by explaining the units values: metric (kg, cm), imperial (lbs, in), and null for region-following. It also clarifies the confirm-gated behavior, though it does not explicitly restate confirm's default value.

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 states a specific verb and resource: setting the default unit system for new clients. It specifies the exact values and scope, making it clearly distinct from sibling tools like get_client_unit_default or get_client_weight_unit.

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?

It explicitly states when the setting applies (new clients and clients added without the app) and when it does not (does not change units a client already chose). It does not name a sibling alternative, but the usage context is clear.

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.