Skip to main content
Glama

get_client_profile

Read-only

Get a client's fitness profile + computed metrics (BMI, TDEE, recommended calories, start/latest logged weight). Pass clientId (the client's user _id, same value every other tool takes). userId is accepted as an alias.

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_client_profile"
  }
}

Input Schema

NameRequiredDescriptionDefault
userIdNo
clientIdNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds real value by disclosing what the response contains (computed metrics plus start and latest logged weight), which matters since there is no output schema; it does not mention behavior when no profile exists or access requirements.

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?

Two sentences, zero waste, with the returned-metrics summary front-loaded and the identifier guidance immediately after.

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 read with no output schema, the description covers both the return contents and the identifier convention. Remaining gaps (empty-profile behavior, coach access prerequisites) are minor but real.

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 description coverage is 0%, so the description carries the full burden and mostly succeeds: it explains that clientId is the client's user _id and is the same value all other tools take, and that userId is an accepted alias. It does not say what happens if both are supplied or if neither is passed.

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 a client's fitness profile') and enumerates the computed metrics returned (BMI, TDEE, recommended calories, start/latest weight). The possessive 'client's' implicitly separates it from get_my_profile and get_organization_profile, but it never names an alternative, so the differentiation is left to inference.

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?

The description tells the agent which identifier to pass but gives no when-to-use or when-not-to-use guidance relative to siblings such as get_client_progress or get_my_profile. Usage is only implied by the resource name.

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.