Skip to main content
Glama

Coline

Create scheduling link

create_scheduling_link

Makes a scheduling link people can book time with the person through, for a length and hours they choose.

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": {
      "workspace": "<workspace>",
      "title": "<title>",
      "durationMinutes": "<durationMinutes>",
      "timeZone": "<timeZone>"
    },
    "name": "create_scheduling_link"
  }
}

Input Schema

NameRequiredDescriptionDefault
slugNoThe link's address; default from the title.
titleYes
isActiveNo
locationNo
timeZoneYes
workspaceYesWorkspace slug from workspaces.list, e.g. "acme".
bookingFlowNoinstant books straight away; proposal and poll wait for the person to pick.
descriptionNo
hostUserIdsNo
conferencingNo
routingRulesNo
embedSettingsNo
openingOptionsNo
schedulingTypeNo
durationMinutesYes
intakeQuestionsNo
availabilityRulesNoBookable hours; default the person's working hours.
bookingWindowDaysNo
bufferAfterMinutesNo
fallbackHostUserIdNo
bufferBeforeMinutesNo
slotIntervalMinutesNo
minimumNoticeMinutesNo
allowBookingOverFocusTimeNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

B3/5.0
Behavior3/5

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

Annotations already declare this is a non-destructive, non-idempotent mutation in a closed world. The description adds one valuable non-obvious trait: the resulting link is bookable by external people, so it is effectively a shareable public artifact. It omits auth/permission requirements, what defaults are applied for the 20 optional fields, and what the create returns.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

One tight sentence with no wasted words and the core purpose front-loaded, but it offers no structure at all for a 24-parameter creation tool, so brevity here reads as under-specification rather than discipline.

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?

Adjusted: given a mutation with 24 params, nested objects, and low schema coverage, the definition is far too thin for an agent to build a valid request without reading the entire schema. An output schema exists, so return values need not be described, but defaults, required-field relationships, and host/routing semantics are unaddressed. Score reflects the severity of the gap relative to tool complexity.

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

Parameters2/5

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

Schema description coverage is only 17% across 24 parameters, so the description must compensate and barely does. 'For a length and hours they choose' loosely maps to durationMinutes and availabilityRules, hinting that hours derive from the person's working hours, but it says nothing about routingRules, openingOptions, intakeQuestions, bookingFlow, schedulingType, or host assignment.

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 specific verb ('Makes') plus resource ('scheduling link') and explains what the artifact enables: people book time with the person for a chosen length and hours. It is clearly a create operation, distinguishable from sibling delete/get/update/list_scheduling_link by the verb alone, though it never names them.

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?

No when-to-use guidance, no prerequisites (e.g. that a workspace slug must be obtained first), and no pointer to update_scheduling_link when the intent is to modify an existing link rather than create a new one. The agent must infer all selection logic.

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