Skip to main content
Glama

Alina Szaputko — Online Consultation Booking

List available online consultation slots

list_available_slots
Read-onlyIdempotent

Read-only. Retrieve current free 60-minute online consultation slots for a date range in Europe/Warsaw. Provide from as a YYYY-MM-DD date and days from 1 to 14 (defaults to 14). Only free slots are returned; no calendar event details or other clients’ information are exposed. This tool cannot reserve a slot, create a booking, or initiate payment.

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": {
      "from": "<from>"
    },
    "name": "list_available_slots"
  }
}

Input Schema

NameRequiredDescriptionDefault
daysNo
fromYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/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 'Read-only' lead-in is redundant; however the description adds genuinely new behavior: only free slots are returned, no calendar details or other clients' data are exposed, and the timezone of the returned slots. It does not describe ordering, empty-result behavior, or slot granularity.

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 safety and scope statement is front-loaded and most sentences carry weight, but the opening 'Read-only' duplicates readOnlyHint and the final negative-capability sentence partly restates 'free slots' semantics.

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 two-parameter read tool with no output schema, the definition covers purpose, parameter formats, timezone, privacy boundaries and the inability to mutate anything — nothing an agent needs to call it correctly is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, yet the description fully compensates: 'from' is documented as a YYYY-MM-DD date and 'days' as an integer 1–14 defaulting to 14, matching the schema's constraints and adding the format the schema omits.

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 names a specific verb and resource ('retrieve current free 60-minute online consultation slots'), plus scope qualifiers (date range, Europe/Warsaw timezone) that make it unmistakable against siblings like create_checkout_session or get_agent_booking_status.

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 clearly delimits what this tool is for by excluding the adjacent workflows ('cannot reserve a slot, create a booking, or initiate payment'), which implicitly routes booking intent to create_checkout_session. It stops short of naming that alternative or stating prerequisites, so it is strong but not fully explicit.

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