Withings MCP

Withings Agent Manifest

withings_agent_manifest

Read-onlyIdempotent

Provides machine-readable install, runtime, and client guidance so AI agents can configure the Withings MCP server without calling Withings or exposing secrets.

Instructions

Machine-readable install, runtime and client guidance for AI agents. Does not call Withings or expose secrets.

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

Input Schema

Name	Required	Description	Default
`client`	No		generic
`response_format`	No		markdown

Output Schema

Name	Required	Default
`links`	Yes
`oauth`	Yes
`client`	Yes	generic
`hermes`	Yes
`package`	Yes
`project`	Yes
`mcp_name`	Yes
`resources`	Yes
`unofficial`	Yes
`agent_rules`	Yes
`standard_tools`	Yes
`troubleshooting`	Yes
`recommended_first_calls`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.4.6Jun 26, 2026

TDQS

A3.9/5.0

Behavior4/5

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

Annotations already indicate read-only, idempotent, non-destructive behavior. The description adds value by explicitly stating it 'does not call Withings or expose secrets', confirming no external side effects or security risks beyond what annotations show.

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 extremely concise with two sentences: the first defines the purpose, and the second clarifies constraints. Every word adds value, and no extraneous information is present.

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 (optional parameters, no required fields, output schema present), the description covers core purpose and safety. However, it could be more complete by mentioning the parameters or the structure of the manifest output, even though output schema exists.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, but the description fails to explain the two parameters ('client' and 'response_format') or their enums. While parameter names and defaults offer some self-evidence, the description does not clarify their purpose, which is necessary given the lack of schema descriptions.

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 tool provides 'Machine-readable install, runtime and client guidance for AI agents' with a specific verb and resource. It distinguishes itself from siblings by explicitly noting it 'Does not call Withings or expose secrets', setting it apart from data retrieval or action tools.

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 implies the tool is for obtaining configuration guidance but does not explicitly state when to use it over alternatives like withings_capabilities or withings_cache_status. No usage exclusions or context are provided, leaving the agent to infer from the name and siblings.

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