Skip to main content
Glama

get_client_preferences

Read-only

The client's own stated constraints — diet type, food allergies, cuisines, meals per day, cooking level, which days they can train, home vs gym, what equipment they actually have, preferred time and session length, plus free-text notes. These are hard constraints, not suggestions: a diet plan that violates dietType, foodAllergies or mealsPerDay is rejected outright by the server, and a workout plan built for equipment they don't own is unusable. Call this BEFORE create_workout_plan/create_diet_plan on every run, including weekly adjustments — clients change these between runs, and the previous plan does not tell you what they say today. Returns null if they have not set any.

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": {
      "clientId": "<clientId>"
    },
    "name": "get_client_preferences"
  }
}

Input Schema

NameRequiredDescriptionDefault
clientIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so safety is covered; the description still adds substantive behavior: downstream server-side enforcement ('a diet plan that violates dietType, foodAllergies or mealsPerDay is rejected outright'), staleness semantics, and the null return when nothing is set. These are non-obvious operational facts an agent must plan around.

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?

The call-before guidance and the hard-constraint warning are front-loaded, and almost every clause carries new information. It is a single dense run-on paragraph, and the long enumeration is slightly heavy, but nothing is truly filler.

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, so the description carries the burden of describing the return: it lists the fields returned and notes the null case for an unconfigured client. For a one-parameter read tool that is complete; no relevant behavior is left implicit.

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 0% for the single clientId parameter, but the parameter is self-evident from its name and the description's repeated 'The client's own stated constraints' framing. No format, lookup, or validation detail is added, so this lands at the adequate-but-minimal baseline.

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 names the exact resource and enumerates its contents ('diet type, food allergies, cuisines, meals per day, cooking level, which days they can train, home vs gym, what equipment they actually have, preferred time and session length, plus free-text notes'). That enumeration lets an agent separate it from adjacent getters like get_client_macro_targets or get_client_intake_form without opening any schema.

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

Usage Guidelines5/5

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

It states an explicit precondition: 'Call this BEFORE create_workout_plan/create_diet_plan on every run, including weekly adjustments.' It also gives the reason (clients change these between runs; the previous plan does not tell you what they say today), which is exactly the guidance an agent needs to avoid caching stale preferences.

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.