Skip to main content
Glama

start_calendly_connect

Get the Calendly sign-in link. Give the URL to the coach to open; bookings then become Trainzilla sessions automatically. (confirm-gated: previews until confirm: true)

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

Input Schema

NameRequiredDescriptionDefault
confirmNoMust be true to actually execute. If false/omitted, returns a preview only.
returnToNoApp path to land on afterwards

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.7/5.0
Behavior4/5

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

Beyond the annotations (readOnlyHint=false, destructiveHint=false, openWorldHint=false), the description discloses two real behaviors: the confirm-gated preview mode and the downstream side effect that bookings flow into Trainzilla sessions. It omits details like link expiry or whether re-invocation replaces an existing connection, which keeps 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.

Conciseness4/5

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

Three short sentences with the core action front-loaded and the confirm caveat placed last as a parenthetical. No filler, though the parenthetical packaging is slightly less scannable than a plain sentence.

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 two-param, no-output-schema connect tool, the description covers what the tool produces (a sign-in URL), who consumes it, and the preview-vs-execute distinction. Only edge details like link lifetime and re-connect behavior are missing.

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%, so the schema already explains both confirm and returnTo. The description restates the confirm-gating semantics, adding emphasis but little information beyond the schema, and says nothing about returnTo. Baseline 3 is appropriate.

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 names a specific verb and resource: get the Calendly sign-in link. The Calendly-specific wording separates it from start_google_calendar_connect without needing to name that sibling. It stops short of explicitly contrasting scope with get_calendly_status or disconnect_calendly, so a 4 rather than 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?

It gives an implied workflow ('Give the URL to the coach to open') and notes what happens next (bookings become Trainzilla sessions). There is no explicit when-not-to-use guidance or routing to alternatives such as get_calendly_status for checking an existing connection, so the agent must infer.

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.