Skip to main content
Glama
Sign In
CallChatSyn MCP Server

CallChatSyn MCP Server

by oneappsworld
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

List open appointment times

list_open_times

Get the next available appointment times in the business's time zone, plus its services and locations, so AI assistants can answer customer booking questions.

Instructions

List the next open appointment times (labels in the business's time zone), plus its services and locations.

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

Input Schema

NameRequiredDescriptionDefault
langNoLabel language

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.4/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 disclosure burden. It usefully states that labels are in the business's time zone and that the response also includes services and locations, but says nothing about how many times are returned, pagination, ordering, or auth requirements.

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?

A single front-loaded sentence with the verb leading and no filler. Every clause (time zone, services, locations) carries information.

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?

For a simple read-only list tool with one fully documented parameter, the description covers the essentials, including the return contents, which matters since no output schema exists. Only pagination/volume behavior is left unstated.

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 the single optional 'lang' enum is fully documented in the schema ('Label language'). The description's mention of 'labels' adds only marginal, indirect context, so the baseline 3 applies.

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 ('List') and resource ('open appointment times') and even notes the label time zone and bundled services/locations. It clearly separates itself from book_appointment, though it never explicitly contrasts with the siblings.

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

Usage Guidelines2/5

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

There is no when-to-use guidance, no prerequisites, and no mention of the natural companion tool book_appointment. The availability-checking intent is only implied by the tool name.

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

Deploy Server

Other Tools