Skip to main content
Glama

Nove: gestação semana a semana

Buscar no nove.care

search_nove
Read-onlyIdempotent

Use para achar no site da Nove o conteúdo sobre um assunto de gestação (enjoo, exames, plano de parto, pressão, remédios na gravidez) ou sobre o app (recursos, preços, enxoval). Retorna até 5 páginas com título, resumo, trecho e link, da mais relevante para a menos.

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": {
      "query": "<query>"
    },
    "name": "search_nove"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryYesO que procurar, em português

Output Schema

NameRequiredDescriptionDefault
itemsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint and openWorldHint=false, so the safety profile is covered. The description adds genuinely new behavior: a cap of 5 results and relevance-descending ordering, which tells the agent how much and what order to expect. It does not cover the empty-result case, which keeps it from a 5.

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 with zero filler: the first front-loads when to use and the scope, the second front-loads the return shape. Every clause carries information an agent needs.

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 one required parameter, full schema coverage, an output schema and rich annotations, the description only needs to add scope and result expectations — both present. The only gap is behavior when no page matches the query, a minor omission given the output schema exists.

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?

Schema coverage is 100% for the single query parameter, so the baseline is 3. The description earns an extra point by constraining the semantic scope of the query — it should describe a pregnancy topic or an app topic, and the schema reinforces Portuguese-language input — which meaningfully guides query formulation beyond the schema's 'O que procurar'.

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?

States a specific verb ('achar') and resource (conteúdo no site da Nove), and enumerates the two content domains covered — pregnancy topics and the app itself. This clearly separates it from the arithmetic-oriented siblings calculate_due_date and get_pregnancy_week without even needing their schemas.

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?

The opening 'Use para achar...' plus concrete example topics (enjoo, exames, plano de parto, preços, enxoval) gives an agent a clear picture of when this tool applies. It stops short of explicit exclusions or naming an alternative tool for out-of-scope queries, so it lands at 4 rather than 5.

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.