Skip to main content
Glama

Nove: gestação semana a semana

Semana da gestação

get_pregnancy_week
Read-onlyIdempotent

Use quando perguntarem sobre uma semana específica da gravidez (4 a 40). Retorna o tamanho do bebê comparado a uma fruta (cm e g), o desenvolvimento do bebê, o que muda no corpo, dicas, perguntas para a consulta, os exames da fase e o link da página. Conteúdo geral em português, com base na Caderneta da Gestante 2026; não é diagnóstico.

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

Input Schema

NameRequiredDescriptionDefault
weekYesSemana da gestação, de 4 a 40

Output Schema

NameRequiredDescriptionDefault
gNo
cmNo
askNo
urlNo
babyNo
bodyNo
tipsNo
weekNo
errorNo
examsNo
fruitNo
trimesterNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint and closed-world, so the safety profile is covered. The description adds genuinely useful context beyond that: the content is general, in Portuguese, sourced from the Caderneta da Gestante 2026, and explicitly not a diagnosis — important framing for a health-content tool.

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 sentences, front-loaded with the trigger condition before the return contents, and no filler. The long enumeration of returned elements is functional rather than padding, since it tells the agent what it can answer with the result.

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

Completeness5/5

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

For a one-parameter lookup with an output schema, annotations, and only one required argument, the definition covers everything an agent needs: when to call it, the valid range, the language and source of the content, and the non-diagnostic caveat.

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% and the single parameter already carries 'Semana da gestação, de 4 a 40'. The description merely restates the same 4-40 range without adding format, edge-case or fallback meaning, so the baseline of 3 applies.

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 states a concrete retrieval action tied to a specific resource ('uma semana específica da gravidez (4 a 40)') and then enumerates exactly what comes back: fruit size comparison in cm/g, baby development, body changes, tips, consultation questions, phase exams, and a page link. That content profile clearly separates it from siblings like calculate_due_date or get_pricing.

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

Usage Guidelines4/5

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

It gives an explicit trigger phrase ('Use quando perguntarem sobre uma semana específica da gravidez') plus the valid 4-40 range, which is real routing context. It stops short of naming alternatives or exclusions, e.g. it never says to use calculate_due_date instead when the user wants a due date rather than week content.

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.