Skip to main content
Glama

Proactive Parent guidance

Pregnancy week guidance

week_guidance
Read-onlyIdempotent

What happens in one week of pregnancy, for a family in any country (the UK, the US and Türkiye have their own guidance; every other country gets general guidance): the baby, the body, tips, and, where the region has them, the appointments and things to do that week. Our own written guidance, with the pages it drew on and links to official pages.

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": {
      "region": "<region>",
      "week": "<week>"
    },
    "name": "week_guidance"
  }
}

Input Schema

NameRequiredDescriptionDefault
weekYesThe week of pregnancy, counted from the first day of the last period (4 to 42).
regionYesWhere the family lives and gets care. GB: the United Kingdom. US: the United States. TR: Türkiye. INTL: general guidance for every other country, such as Germany, India or Brazil. Required, with no default, because care differs between countries: guidance is never taken from another region.
languageNoThe language to answer in. If the region's guidance is not written in it, the region's own language is used (GB and US: en; TR: tr; INTL: en, tr, es, fr).
multiplesNoTrue for twins or more.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive, closed-world behavior, so the safety profile needs no restating. The description does add real value beyond them by disclosing the content structure and the provenance model ('our own written guidance, with the pages it drew on and links to official pages'), which tells the agent the output is sourced and citation-bearing. It says nothing about length, caching, or fallback behavior when a region lacks a section, leaving some behavioral gaps.

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

Conciseness4/5

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

The core idea is front-loaded ('What happens in one week of pregnancy'), and the two sentences cover scope and provenance without padding. The nested parentheticals about which countries have their own guidance make it denser to parse than necessary, but nothing is wasted.

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?

With no output schema, the description carries the burden of describing return content and does so: the baby, the body, tips, regional appointments, plus source pages and official links. Combined with a fully documented input schema and rich annotations, an agent has enough to call this correctly; only output format details (structure, length) are absent.

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 description coverage is 100% and the schema already spells out region semantics, language fallback rules, and the week range, so the description cannot add much. Its only contribution is reinforcing that guidance is never borrowed across regions. Baseline 3 applies when the schema does the heavy lifting.

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

Purpose4/5

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

The description names a specific resource (one week of pregnancy guidance) and enumerates what it returns: the baby, the body, tips, and regional appointments/things to do. It also clarifies the regional split (UK, US, Türkiye specific; general elsewhere), so an agent knows exactly what content this tool produces. It stops short of explicitly contrasting itself with the age_guidance sibling.

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?

Usage is implied rather than stated: an agent can infer this is the tool for pregnancy-week questions for a family in a given region. There is no explicit when-to-use/when-not, and no routing guidance toward or away from the age_guidance sibling, which an agent would have to reason about unaided.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources