Skip to main content
Glama
Sign In
technogym-mcp

technogym-mcp

by ErikAnkerKilbergSkallevold
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

get_account_info

Check if your Technogym mywellness credentials are valid by logging in and retrieving user profile, culture, and associated facilities.

Instructions

Log in (if needed) and return the mywellness user id, name, culture and facilities.

Use this to verify credentials are working.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.4/5.0
Behavior4/5

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

With no annotations, the description carries the burden. It discloses the key behavioral trait: the tool may log in and is meant to validate credentials. It does not mention session side effects or errors, but the main auth behavior is exposed.

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 short sentences, with the action and return contents front-loaded and the usage intent in the second sentence. No redundant phrasing.

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-parameter, low-complexity tool with an output schema, the description is nearly complete: it covers purpose, auth behavior, and intended usage. It could mention when not to use it or any prerequisites, but nothing critical is missing.

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 schema fully covers this dimension. The description appropriately adds no parameter details; baseline 4 applies.

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 action ('Log in (if needed)') and the exact resource returned ('mywellness user id, name, culture and facilities'). This clearly distinguishes the tool from the workout/session-focused siblings.

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?

Explicitly gives a use case: 'Use this to verify credentials are working.' It does not name alternatives or exclusions, but the sibling names make the intended context clear.

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

Deploy Server

Other Tools