Skip to main content
Glama

Szülni Jó – services and appointments

Szolgáltatások és foglalási módok

list_booking_services
Read-onlyIdempotent

Online foglalható WooCommerce-szolgáltatások és WooCommerce-termék nélküli, csak telefonon foglalható szolgáltatások. Név, foglalási mód, online ár és link vagy telefonszám. Ezzel keresd meg a service_id értéket; ne találj ki azonosítót.

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

Input Schema

NameRequiredDescriptionDefault
queryNoOpcionális keresés a szolgáltatás vagy szakember nevében.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint=false and destructiveHint=false, so safety is covered. The description adds value beyond that by enumerating the returned fields — useful because there is no output schema — and by warning against inventing identifiers. It does not mention pagination, result limits, or empty-result behavior.

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?

Three short sentences, each carrying distinct information: what is listed, what is returned, and how to use the result. The core scope statement is 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.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a single-optional-parameter, read-only listing tool with rich annotations, the definition covers scope, return fields, and the ID-lookup workflow, which is what an agent needs. The only gap is that it does not position itself relative to get_available_appointments, leaving the agent to infer which tool answers an availability question.

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 description coverage is 100%: the single optional query parameter is documented in the schema as a search over service or specialist name. The description adds no further semantics about the parameter, so the baseline of 3 applies.

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 description names the exact resource set: online-bookable WooCommerce services plus phone-only services that have no WooCommerce product, and lists the fields returned (name, booking mode, online price, link or phone number). This is a specific verb+resource statement an agent can act on. It stops short of explicitly contrasting with the sibling get_available_appointments, so it is clear but not fully differentiated.

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?

"Ezzel keresd meg a service_id értéket; ne találj ki azonosítót" gives concrete workflow guidance: call this to obtain a valid service_id and never fabricate one. That is a clear use condition tied to a downstream need. It offers no explicit when-not-to-use rule or named alternative for availability checks, which keeps it below 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