Skip to main content
Glama

get_pregnancy_summary

Read-only

Retrieves pregnancy summary data from Garmin Connect so users can review pregnancy-related health metrics in an MCP client.

Instructions

Get pregnancy summary data

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.7/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=true, so the safety profile is covered structurally. The description adds nothing beyond the name — not what entity it is scoped to (the authenticated user?), what period it covers, or what the response contains, which matters given no output schema.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

At five words it is certainly front-loaded and contains no filler. But brevity here is under-specification rather than economy — the single sentence carries no scoping, format, or routing information that would earn its place as a complete definition.

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?

With zero parameters, no output schema, and only generic annotations, the description is the sole carrier of domain context and it provides almost none. An agent cannot tell what the returned summary comprises or how it differs from adjacent summary endpoints, which is a material gap for a data-retrieval tool.

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 input schema is an empty object with no parameters at all, so per the baseline there is nothing for the description to disambiguate. It does not, however, clarify the implicit scoping (whose pregnancy data, over what window) left unspecified by the empty schema.

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 description names a verb (Get) and a resource (pregnancy summary data), so the broad intent is legible. However, 'summary data' is vague about contents and scope — whether it returns a current snapshot, a lifespan aggregate, or a fixed set of fields — and nothing distinguishes it from the many other *_summary siblings beyond the word 'pregnancy'.

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, no prerequisite or scope statement, and no naming of alternatives among the long list of summary tools. The agent must infer that this is the pregnancy-specific counterpart of get_sleep_summary, get_stress_summary, etc. purely from the name.

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