Skip to main content
Glama
Sign In
Withings MCP Server

Withings MCP Server

by Schimmilab
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

get_authorization_url

Get an OAuth2 authorization URL to authenticate users with Withings, granting access to health data such as body measurements, activity, and sleep analysis.

Instructions

Get OAuth2 authorization URL to authenticate with Withings

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

Input Schema

NameRequiredDescriptionDefault
scopeNoOAuth scopes (comma-separated): user.info, user.metrics, user.activityuser.info,user.metrics,user.activity

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior2/5

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

No annotations are provided, so the description must fully disclose behavioral traits. It only states that the tool gets a URL, with no mention of side effects (none expected), rate limits, or user interaction required. This leaves the agent with minimal understanding of the tool's behavior beyond the basic action.

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?

The description is a single, front-loaded sentence with no unnecessary words. Every part is essential, making it highly efficient.

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?

Given the tool's simplicity (one optional param, no output schema), the description is largely sufficient. However, it could briefly mention that the URL requires user interaction to complete authentication, but this is not critical for a tool that simply returns a URL.

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 coverage is 100% for the single parameter 'scope', and the description does not add any extra meaning beyond the schema's own description. As per guidelines, with high schema coverage the baseline is 3, and the description provides no additional value.

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 clearly states the action ('Get'), the resource ('OAuth2 authorization URL'), and the target ('authenticate with Withings'). It is specific and easily distinguishable from sibling tools which are all data retrieval functions.

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 does not provide explicit guidance on when to use this tool vs alternatives, such as indicating it should be called first before other API calls. The context implies it is for authentication, but no direct instructions or exclusions are given.

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