mcp-google-health

update_profile

Modify Google Health profile fields by listing each changed field in updateMask, so only intended profile data is updated.

Instructions

Update profile fields. Name each changed field in updateMask.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "profile": "<profile>",
      "updateMask": "<updateMask>"
    },
    "name": "update_profile"
  }
}

Input Schema

Name	Required	Description	Default
`profile`	Yes	Profile fields. See describe_schema Profile.
`updateMask`	Yes	Comma-separated field paths to change.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Nov 10, 2026

TDQS

C2.7/5.0

Behavior2/5

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

Annotations already declare readOnly=false, destructive=false, openWorld=true, so the safety profile is covered. The description adds nothing beyond that: it does not say whether fields absent from updateMask are preserved, what happens with an invalid field path, whether this replaces or patches state, or that permissions may be required. For a mutation tool that is a real gap.

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, action first, then the one operative constraint. No filler and nothing buried.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

This is an open-world mutation with a nested free-form profile object and no output schema. The description leaves the caller without the patch-vs-replace semantics, without noting that valid field paths come from describe_schema Profile (only the schema hints at it), and without any error or permission context. It is too thin for the tool's complexity.

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%, so both parameters are already documented, including "Comma-separated field paths to change" for updateMask. The description's "Name each changed field in updateMask" reinforces partial-update semantics but adds no syntax, format, or edge-case detail beyond the schema. Baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The verb+resource ("Update profile fields") is stated, so an agent knows this mutates the profile. But "profile fields" is left undefined and the description never distinguishes this from nearby mutators like update_settings or update_data_point. It is minimally adequate rather than differentiating.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no when-to-use guidance and no mention of the alternative mutation siblings (update_settings, update_data_point). The only directive, "Name each changed field in updateMask," is an invocation instruction rather than a statement of context or exclusion.

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