Skip to main content
Glama

Minik Günlük

About the Minik Günlük app

get_app_info
Read-onlyIdempotent

What the Minik Günlük app is (school-family app for nurseries and preschools: daily meals, sleep, toilet, mood, activity photos, medicine tracking at school and home, messages, appointments and video calls with the teacher), App Store / Google Play links and the demo request page for schools (https://minikgunluk.com.tr/demo). Contains no prices: for pricing, point schools to the demo page. TR: Minik Günlük uygulaması nedir, nereden indirilir, okullar için tanıtım/demo. Fiyat bilgisi yok.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

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, non-destructive and openWorldHint=false, so safety is covered. The description adds genuinely non-obvious context beyond that: the absence of pricing data, the presence of store download links and a school demo URL, and the school/family framing of the audience.

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 substantive content is front-loaded in a single dense sentence that enumerates exactly what the agent will get. The trailing Turkish sentence restates the same facts for localization, which is redundant for a reader of the English text but a deliberate pattern rather than padding or 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?

For a zero-parameter, read-only informational tool with no output schema, the description covers what is returned, what is deliberately excluded (pricing), and where to redirect for the excluded case. Nothing an agent needs in order to call it or interpret the result 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?

The tool takes zero parameters and the schema is an empty object, so there is nothing for the description to disambiguate. Baseline of 4 applies; no parameter meaning is missing because none exists.

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 precisely what this tool returns: an overview of what the Minik Günlük app is, with an explicit enumeration of covered domains (meals, sleep, toilet, mood, photos, medicine, messages, appointments, video calls), plus store links and the demo page. That content scope clearly separates it from get_parent_guide, list_videos and search_parent_guides, which handle individual guide 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?

It gives a concrete usage rule: the tool contains no prices, so for pricing the agent should point schools to the demo page (https://minikgunluk.com.tr/demo). That is real when-to-use guidance. It stops short of naming a sibling tool as the alternative for other content types, so routing is implied rather than spelled out.

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