Skip to main content
Glama

Minik Günlük

Search parenting guides for preschool children

search_parent_guides
Read-onlyIdempotent

Search Minik Günlük's free parenting guides (in Turkish) for children aged 0-6: nursery/kindergarten adjustment, sleep, eating, toilet training, tantrums, screen time, going to school when sick, medicine safety at home, play, sibling jealousy, talking with the teacher. Returns title, summary, category, age range, reading time, article URL and up to 3 practical tips. Call with no arguments to list the latest guides. Always show the article URL to the user. Guides are general information, not medical advice. TR: Okul öncesi çocuk ebeveyn rehberi makalelerinde arar; ör. query "kreşe uyum", "uyku düzeni", "tuvalet eğitimi", "öfke nöbeti", "ekran süresi", "ateşli çocuk okula gider mi", "kardeş kıskançlığı".

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": "search_parent_guides"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMax results, 1-10 (default 5). / En çok sonuç (varsayılan 5).
queryNoKeywords in Turkish or English, e.g. "uyku", "tantrum", "tuvalet eğitimi". Optional. / Anahtar kelime (isteğe bağlı).
categoryNoOptional category filter as published on the site (e.g. "Uyku", "Beslenme", "Okula uyum"). / İsteğe bağlı kategori.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Adds real context beyond the annotations: results include title, summary, category, age range, reading time, article URL and up to 3 tips; the agent is told to always show the URL and that content is general information, not medical advice. Annotations already cover read-only/idempotent safety, so this is a solid supplement rather than a full behavioral spec.

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 English portion is front-loaded and dense with useful facts, but the appended TR sentence largely duplicates the topic/keyword examples already listed, adding length without new information for a non-Turkish-reading agent.

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 simple three-optional-parameter search with no output schema, the description covers scope, return fields, default behavior, display requirement and a disclaimer about medical advice. Nothing needed to invoke it correctly is missing.

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 each parameter already documents its meaning and default. The description adds example queries in Turkish (e.g. "kreşe uyum", "öfke nöbeti") and the category concept, plus the no-argument default behavior, but adds no syntax or matching rules beyond the schema.

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 (search) plus the resource (Minik Günlük's free parenting guides in Turkish for ages 0-6) and enumerates covered topics. It is clearly distinct from siblings like get_parent_guide, which fetches a single article rather than searching.

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 says to call with no arguments to list the latest guides, and the schema makes all filters optional. It does not name the sibling to use once a guide is found, but the search-vs-fetch distinction is clear from the tool set.

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