Skip to main content
Glama

Freie Termine

check_availability
Read-only

Freie Termine für eine Leistung (serviceId aus list_services). Zeitraum als ISO-Datum mit Uhrzeit und Zeitzone.

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": {
      "serviceId": "<serviceId>"
    },
    "name": "check_availability"
  }
}

Input Schema

NameRequiredDescriptionDefault
toNoEnde des Zeitraums, ISO 8601
fromNoBeginn des Zeitraums, ISO 8601
serviceIdYesKennung der Leistung aus list_services

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior3/5

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

The readOnlyHint annotation already tells the agent this is a safe read, so the description only needs to add behavior. It contributes the format constraint that the range must include time and timezone, but says nothing about default window when from/to are absent, maximum range, or whether returned slots are already filtered by availability rules.

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?

Two short sentences with the resource first and the format constraint second; nothing is padded. It is telegraphic to the point that a few words of connecting context would not have hurt, but it earns its length.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

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

For a simple read-only tool with full schema coverage and no output schema, the basics are covered. Missing is what the call returns (a list of free slots?) and how the optional from/to behave when omitted, which matters because only serviceId is required and there is no output schema to explain the result.

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 all three parameters carry their own descriptions, so the schema does the heavy lifting. The description only adds a timezone requirement beyond the schema's 'ISO 8601' note and repeats the list_services provenance already present in the serviceId description.

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?

Names a concrete resource and outcome: free appointment slots for a given service, with the key input (serviceId) identified. That distinguishes it adequately from book_appointment and list_services, though the terse phrasing leaves the read-only lookup nature to be inferred rather than stated.

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

Usage Guidelines3/5

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

Points the agent to list_services as the source of serviceId, which is a useful upstream-workflow hint. It gives no guidance on when from/to should be supplied, what happens if the range is omitted (only serviceId is required), or any precondition such as the service being bookable.

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