Skip to main content
Glama

plateau-candy

get_availability

Read-only

Check available time slots for a consultation with Plateau Candy. Requires an event_type_id from get_services; returns bookable slots per day in Europe/Berlin time.

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": {
      "event_type_id": "<event_type_id>",
      "start_date": "<start_date>",
      "end_date": "<end_date>"
    },
    "name": "get_availability"
  }
}

Input Schema

NameRequiredDescriptionDefault
end_dateYesEnd date (YYYY-MM-DD), max 14 days from start
start_dateYesStart date (YYYY-MM-DD)
event_type_idYesEvent type ID (get from get_services first)

Output Schema

NameRequiredDescriptionDefault
slotsYes
timezoneYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, so the safe-read profile is known; the description adds useful context beyond that: results are per-day bookable slots in Europe/Berlin time. No mention of rate limits, empty-result behavior, or what the returned slots include, but the output schema covers return shape.

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 tight sentences with no filler, and the core purpose is front-loaded before the dependency note. Slightly compressed for a read tool with a real prerequisite, but efficient.

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?

Complete for a low-complexity availability query: prerequisite, timezone, and result granularity are stated, and the output schema documents the return value. Minor omissions are empty-response behavior and the next-step relationship to book_consultation.

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%, so all three parameters are already documented, including the date format and the 14-day maximum. The description's note that event_type_id comes from get_services largely restates the schema, adding only the timezone framing; baseline 3 is appropriate.

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 (check) and resource (available time slots) plus scope (consultation with Plateau Candy), and names the sibling get_services as the source of the required ID. An agent can distinguish it from book_consultation without reading either schema.

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?

Gives a concrete prerequisite: an event_type_id must come from get_services first, which routes the agent correctly. It does not say explicitly that this is the step preceding book_consultation, nor when not to use it, so it stops short of full when/when-not guidance.

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