Skip to main content
Glama

Minik Günlük

Get a parenting guide

get_parent_guide
Read-onlyIdempotent

Get the full text of one Minik Günlük parenting guide by its slug (from search_parent_guides) or its minikgunluk.com.tr/rehber URL: all sections, tips, FAQ, sources and the article URL. Summarize for the user and always include the article URL. Do not add diagnoses, doses or treatments; suggest consulting a pediatrician. TR: Rehber makalesinin tamamı (bölümler, ipuçları, sık sorulan sorular, kaynaklar).

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": {
      "slug": "<slug>"
    },
    "name": "get_parent_guide"
  }
}

Input Schema

NameRequiredDescriptionDefault
slugYesGuide slug or URL, e.g. "krese-uyum" or "https://minikgunluk.com.tr/rehber/krese-uyum". / Makale kısa adı ya da adresi.

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 readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description goes beyond them by enumerating the returned content (all sections, tips, FAQ, sources, article URL) and by imposing an editorial safety policy, which an agent would otherwise not know. It stops short of describing edge cases such as a missing slug, which keeps it off 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.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The English portion is front-loaded with the resource and keying options, then the output summary, then the safety rule. The appended Turkish sentence largely restates the same return-content list, which is mild redundancy rather than confusion.

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?

There is no output schema, so the description carries the burden of explaining what comes back, and it enumerates the sections returned plus the article URL. Combined with the usage and safety instructions, an agent has everything needed to call it and present the result correctly.

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 schema already gives examples of both slug and URL forms, so the description adds little parameter detail. It does add provenance for the slug (from search_parent_guides), but that duplicates the schema examples rather than extending them.

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 and resource ('Get the full text of one Minik Günlük parenting guide') and immediately identifies the two keying options (slug or minikgunluk.com.tr/rehber URL). This clearly distinguishes it from search_parent_guides, which is named as the source of slugs.

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

Usage Guidelines5/5

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

Explicitly says to get the slug from search_parent_guides or accept a full URL, directs the agent to summarize and always include the article URL, and sets a hard content boundary (no diagnoses, doses or treatments; suggest a pediatrician). That is when-to-use, how-to-use and a do-not instruction in one place.

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