Skip to main content
Glama
Sign In

motherwise

by io.github.giachi85it-ux
OverviewDiscussionsAdmin

get_maternity_facts

PAID $0.05 via x402 (USDC micropayment over HTTP 402). Returns a single source-linked, date-verified fact about the maternity system in the Netherlands or Hungary — e.g. kraamzorg (Dutch postnatal care), midwife/verloskundige access, maternity and parental leave, Hungarian CSED/GYED benefits, and key registration deadlines. Set 'country' to 'nl' or 'hu' and 'topic' to keywords (e.g. 'leave', 'kraamzorg', 'GYED'). Returns the id, topic, question, answer, the source name and URL, the verified date, and a verification block. Returns an error if no verified entry matches the filter.

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

Input Schema

NameRequiredDescriptionDefault
topicNoKeywords for the fact wanted, e.g. 'leave', 'kraamzorg', 'GYED'. Optional.
countryNoCountry: 'nl' (Netherlands) or 'hu' (Hungary). Optional; omit to search both.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / country / description
      Added value: +"Country: 'nl' (Netherlands) or 'hu' (Hungary). Optional; omit to search both."
    • addedInput schema / properties / topic / description
      Added value: +"Keywords for the fact wanted, e.g. 'leave', 'kraamzorg', 'GYED'. Optional."
  2. Added

TDQS

A4.7/5.0
Behavior5/5

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

With no annotations provided, the description carries the full burden and does so excellently. It discloses the $0.05 x402 payment requirement, the source-linked and date-verified nature of results, the exact return fields, and the error condition when no verified entry matches.

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?

The description is dense but every segment earns its place: payment, scope, example topics, parameter usage, return fields, and error behavior. Key constraints are front-loaded, and there is no filler.

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?

Despite having no output schema, the description fully enumerates the return payload: id, topic, question, answer, source name/URL, verified date, and verification block. Both optional parameters are explained, the payment model is disclosed, and failure behavior is stated. Nothing an agent needs to invoke this correctly is missing.

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%, so the baseline is 3. The description adds meaningful value beyond the schema by illustrating example keyword values like 'leave', 'kraamzorg', and 'GYED', and by clarifying that country is optional and omitting it searches both countries.

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 specific verb and resource: returns a single source-linked, date-verified fact about maternity systems in the Netherlands or Hungary. It names concrete topics and examples, making it clearly distinct from the sibling tools like ask or get_affirmations.

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 description gives clear usage instructions: set 'country' to 'nl' or 'hu' and 'topic' to keywords, and notes that omitting country searches both. It does not explicitly name alternatives or when not to use this tool, but for this self-contained factual lookup tool the guidance is strong.

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

All motherwise toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources