Skip to main content
Glama

Szülni Jó – services and appointments

Szabad időpontok keresése

get_available_appointments
Read-onlyIdempotent

Az adott szolgáltatás szabad, jövőbeli időpontjai. Előbb kérd le a service_id értéket. online módnál termékoldali linket, phone módnál telefonszámot és Csak telefonon foglalható jelölést mutass. A lekérdezés nem foglal és nem tart fenn időpontot.

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": {
      "service_id": "<service_id>"
    },
    "name": "get_available_appointments"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
offsetNo
date_toNoYYYY-MM-DD, legfeljebb ma +119 nap. Alapérték: a kezdőnaptól 30 napos időszak.
date_fromNoYYYY-MM-DD, legkorábban ma (Europe/Budapest). Alapérték: ma.
service_idYesA list_booking_services által visszaadott azonosító.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent and non-destructive, so the safety profile is covered. The description still adds real value beyond them: it states explicitly that the query neither books nor reserves an appointment, and it explains that booking channel (online vs phone) changes what must be shown to the user.

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?

Four short sentences with the resource definition front-loaded, followed by prerequisite and presentation rules. Nothing is redundant, though the presentation rules sit slightly apart from the tool's own semantics.

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, the description carries the burden of describing returns and does so partially, explaining what each booking mode yields (link vs phone number plus a 'bookable only by phone' marker). Pagination behavior and result ordering remain unaddressed.

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 60%: service_id, date_from and date_to are documented, while limit and offset are not described in either place. The description only reinforces the service_id prerequisite already stated in the schema, so it does not compensate for the undocumented pagination parameters.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The opening sentence names a specific resource and scope: free future appointments of a given service. It does not name the sibling tool in prose (the prerequisite is stated generically as 'first fetch the service_id value'), so it is clear but not fully differentiated against list_booking_services.

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 explicit sequencing guidance ('Előbb kérd le a service_id értéket') and tells the agent how to present results differently for online vs phone modes. It does not state when not to use this tool or name an alternative, which keeps it below a 5.

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