Skip to main content
Glama

Belline Connect

Get free times

get_availability
Read-onlyIdempotent

Free times for a business, from its own booking engine. Answers one of three ways: 'slots' (real free times), 'windows' (the hours the business is open, for a business with no diary of people; NOT free times, the owner confirms the visit time) or 'request' (the business confirms every request itself). Never invents a time. At most 14 days.

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": {
      "slug": "<slug>"
    },
    "name": "get_availability"
  }
}

Input Schema

NameRequiredDescriptionDefault
toNoLast date, YYYY-MM-DD. Optional, defaults to a week on.
fromNoFirst date, YYYY-MM-DD. Optional, defaults to today.
slugYesBusiness slug.
service_idNoA service id from get_business_profile. Optional.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already cover safety (readOnly, idempotent, non-destructive, closed-world), and the description adds genuinely new behavior: three distinct answer modes with their meanings, a 'never invents a time' guarantee, and a hard 14-day span cap. It does not describe failure or empty-result behavior, keeping it from a 5.

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?

Four compact sentences, front-loaded with what the tool returns and immediately qualifying the three modes. Every sentence carries information; nothing is padding.

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?

With no output schema, the description takes on the burden of explaining return shape and does so via the slots/windows/request taxonomy plus the range cap. It leaves the per-result fields and empty-range behavior unexplained, so it is strong but not exhaustive.

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?

Schema coverage is 100%, so the parameters are already documented; the baseline would be 3. The description adds a real constraint not present in the schema ('At most 14 days'), which materially affects how from/to must be set.

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?

States a concrete verb+resource ('free times for a business') and specifies the source ('from its own booking engine'), which separates it from directory-style siblings like search_businesses. It does not explicitly name or contrast a sibling tool, so it stops short of a 5.

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?

Usage is implied rather than stated: an agent infers you call this before book_slot or create_inquiry. The 'windows' caveat ('NOT free times, the owner confirms the visit time') is valuable interpretation guidance, but there is no explicit when-to-use / when-not-to-use routing to alternatives.

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