Skip to main content
Glama
fitdays-mcp-server

fitdays-mcp-server

by brad28820

List FitDays users

list_users

Retrieve all sub-users registered under a FitDays account with their stable suid, nickname, sex, birthday, height, and target weight, so you can query data for the correct person.

Instructions

List the sub-users (people) registered under the FitDays account. Each user has a unique and stable suid, used by other tools to query data for that user. Returns a list where each entry contains nickname, sex (male or female, biological sex), birthday, height_cm, target_weight_kg (user-set target weight), suid, and uid (account uid).

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.2.1

TDQS

A3.7/5.0
Behavior3/5

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

No annotations exist, so the description carries the full behavioral burden. It does disclose the read-only nature implicitly (a list operation) and adds valuable semantics such as `suid` being 'unique and stable' and `sex` meaning biological sex, but it says nothing about ordering, pagination, result limits, or authentication requirements. Useful context without a complete behavioral picture.

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?

Three short sentences, front-loaded with the purpose, followed by the identifier's meaning, then the returned fields. No filler or restatement of the title, and every clause adds information an agent would otherwise lack.

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?

With no output schema, the description compensates by enumerating every returned field (`nickname`, `sex`, `birthday`, `height_cm`, `target_weight_kg`, `suid`, `uid`) and clarifying ambiguous ones. For a zero-parameter listing tool this is close to complete; only pagination or ordering behavior is unstated.

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 zero parameters, so the baseline of 4 applies. The description correctly adds no parameter guidance because none is needed, and instead spends its words on return-field meaning.

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 gives a specific verb and resource: 'List the sub-users (people) registered under the FitDays account.' It also defines the key identifier (`suid`) and its downstream role, which lets an agent tell this apart from the sibling weight/device tools. It stops short of explicitly contrasting itself with any named sibling, so a 5 is not warranted.

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?

There is no explicit when-to-use section or named alternative. Usage is only implied via the note that `suid` is 'used by other tools to query data for that user,' which hints this is a prerequisite discovery call, but the agent must infer that itself. Adequate minimum, not instructive.

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