Skip to main content
Glama
mcp-starter-kit

mcp-starter-kit

by 0xJRP

Check availability

check_availability

Returns currently open appointment or booking slots so customers can see available times and choose when to book.

Instructions

Returns the currently open appointment or booking slots. Use this when a customer wants to book or asks what times are available.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.8/5.0
Behavior3/5

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

With no annotations, the description carries the full burden; it implies a safe read by saying it "returns" open slots, which is useful. However, it never defines what "currently" covers (today, this week, a default horizon), nor any timezone or permission assumptions. For a slot-lookup tool feeding a booking decision, that ambiguity is a real gap but not a contradiction.

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?

Two short sentences, front-loaded with what the tool returns followed by when to use it. Every sentence carries information and nothing is padded.

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 zero-parameter, no-output-schema tool the description is nearly sufficient, but because no output schema exists the agent gets no idea of the returned slot shape, count, or time range. The vague "currently" is the one detail an agent would most need to set expectations with a customer.

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

Parameters4/5

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

The tool takes zero parameters, so there is nothing for the description to disambiguate; baseline 4 applies. It correctly implies the result set is unfiltered by any caller-supplied date or resource.

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 uses a specific verb and resource ("Returns the currently open appointment or booking slots"), which is far more informative than the tautological title "Check availability". It doesn't explicitly contrast with siblings like price_quote or get_business_info, but those occupy clearly different domains, so 4 rather than 5 is appropriate.

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 states a concrete trigger condition: use when a customer wants to book or asks what times are available. There is no explicit when-not guidance or mention of how it relates to price_quote for a complete booking flow, which keeps it at 4.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.