Skip to main content
Glama

Explore BV, yeast, UTI and prevention education

get_intimate_health_education
Read-onlyIdempotent

Read a general, unranked comparison of BV, vaginal yeast and UTI, with linked prevention and recurrence research on probiotics, D-mannose and other options, plus an interactive learning guide. Accepts no inputs: never send symptoms, quiz answers, selections or personal details. This is education and question preparation, not symptom assessment, diagnosis, treatment selection or individual eligibility.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

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, destructiveHint=false and openWorldHint, so the safety profile is largely covered. The description adds genuinely non-redundant behavior: it accepts no inputs and explicitly forbids sending symptoms, quiz answers, selections or personal details — a data-handling constraint the annotations cannot express.

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?

Two sentences, front-loaded with what the resource contains before the negative constraints. The prohibition list is somewhat dense but every element (symptoms, quiz answers, selections, personal details) maps to a real misuse risk. Reasonably tight with no filler.

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 and no parameters, the description must convey what comes back, and it does: a general unranked comparison, linked prevention/recurrence research on probiotics and D-mannose, and an interactive guide. Response format/structure is not specified, but for an informational read-only tool this is close to sufficient.

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?

Zero parameters, so the baseline is 4. The description reinforces this with 'Accepts no inputs', confirming the empty schema and warning against accidental payloads. There is no parameter semantics left to add.

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 (Read) and a concrete resource: an unranked comparison of BV, vaginal yeast and UTI, plus prevention/recurrence research and an interactive learning guide. That scope is clearly distinguishable from siblings like get_service_details, list_care_options or get_online_care_boundaries, which cover services and policy rather than clinical education content.

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?

Explicitly carves out when the tool must not be used ('not symptom assessment, diagnosis, treatment selection or individual eligibility'), which is strong usage guidance. It does not however name a sibling alternative for users who do want symptom assessment or eligibility, leaving the routing decision partly to inference.

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