Skip to main content
Glama
Sign In
Calendly MCP Server

Calendly MCP Server

by meAmitPatil
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

get_oauth_url

Generate a Calendly OAuth authorization URL for user authentication. Specify a redirect URI and optional state parameter for security.

Instructions

Generate OAuth authorization URL for user authentication

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": {
      "redirect_uri": "<redirect_uri>"
    },
    "name": "get_oauth_url"
  }
}

Input Schema

NameRequiredDescriptionDefault
stateNoOptional state parameter for security
redirect_uriYesThe redirect URI for your OAuth application

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.0.0

TDQS

A3.5/5.0
Behavior2/5

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

With no annotations, the description carries the full burden of behavioral disclosure. It does not mention side effects, validation behavior, required external setup, or return format, leaving the agent without important context about how the tool behaves.

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?

The description is a single, concise sentence that earns its place without redundancy. It is front-loaded with the action and resource, making it easy to parse quickly.

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?

The tool is simple and the description gives a clear basic purpose, but with no output schema and no annotations, the description should at least clarify that it returns the URL and note any relevant context (e.g., OAuth flow position). It is adequate but leaves gaps.

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?

The schema provides 100% parameter coverage with descriptions for both parameters. The description adds no additional meaning beyond what the schema already states, so a baseline score of 3 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description uses a specific verb ('Generate') and resource ('OAuth authorization URL'), clearly stating its purpose. It differentiates from siblings like exchange_code_for_tokens and refresh_access_token, which handle subsequent OAuth steps.

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?

The phrase 'for user authentication' implies the tool is used to start the OAuth flow. However, it provides no explicit guidance on when to use this tool versus alternatives, nor any exclusions or prerequisites.

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