Skip to main content
Glama

get_user_settings

Read-onlyIdempotent

Get the user's workout settings: unit preference (lbs/kg), weight rounding, and the defaults new workouts get for the warmup step and waiting for the lap button between exercises.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
unitsYes
weight_roundingNo
skip_last_rest_stepNo
default_warmup_enabledYesNew workouts start with the open warmup step unless the request says otherwise.
default_wait_for_lap_enabledYesNewly added exercises wait for a lap button press before the next exercise unless the request says otherwise.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • addedOutput schema / properties / default_wait_for_lap_enabled
      Added value: +{
      +  "description": "Newly added exercises wait for a lap button press before the next exercise unless the request says otherwise.",
      +  "type": "boolean"
      +}
    • addedOutput schema / properties / default_warmup_enabled
      Added value: +{
      +  "description": "New workouts start with the open warmup step unless the request says otherwise.",
      +  "type": "boolean"
      +}
    • changedOutput schema / required
      Previous value: -[
      -  "units"
      -]New value: +[
      +  "units",
      +  "default_warmup_enabled",
      +  "default_wait_for_lap_enabled"
      +]
  2. First observed

TDQS

A3.7/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and closed-world scope, so the safety profile is fully covered. The description adds the specific setting dimensions that come back, which helps an agent judge whether this tool holds the data it needs, but says nothing about auth, caching, or fallback behavior when settings are unset.

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?

A single front-loaded sentence that names the resource first and then the returned fields, with no filler, repetition, or hedging. Every clause carries information an agent would otherwise have to discover by calling the tool.

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 zero-param read with an output schema and full annotation coverage, the description supplies everything needed to select and invoke it. The only residual gap is what happens when the user has no configured settings, which the output schema presumably resolves anyway.

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?

The tool takes no parameters, so there is nothing for the description to disambiguate; the baseline of 4 applies. The parenthetical '(lbs/kg)' incidentally documents the value domain of the unit setting the tool returns.

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?

States a specific verb and resource ('Get the user's workout settings') and enumerates the exact contents: unit preference (lbs/kg), weight rounding, and new-workout defaults for warmup step and lap-button waiting. This is concrete enough to distinguish it from data-oriented siblings like get_training_maxes or get_coach_profile, though it never names those alternatives explicitly.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is only implied: an agent can infer it should call this before computing or displaying anything in weight units, but the description never states when to use it, when not to, or what to consult instead. For a zero-parameter getter the gap is small, but no guidance is actually written.

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