Skip to main content
Glama

IRM Consulting & Advisory

Create a booking link

create_booking_link

Create a single-use Calendly link for a free 30-minute consultation with IRM. Give the link to the person; they choose a time and confirm on Calendly, which sends the confirmation. This tool books nothing itself and takes no personal data.

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

Input Schema

NameRequiredDescriptionDefault
sourceNoOptional short name of the calling assistant or agent, e.g. "claude" (attribution only).
serviceNoOptional service id the consultation is about (attribution only).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=false, openWorldHint=true and non-idempotent, and the description adds real context beyond them: the link is single-use, no personal data is captured, the tool does not perform the booking, and Calendly sends the confirmation. It omits link expiry duration and any rate limits, which are the remaining behavioral unknowns.

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?

Three short sentences, front-loaded with what is created and followed by the handoff workflow and the key negative guarantee. Every sentence carries distinct information with no repetition of the title.

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 zero-required-parameter, non-destructive creation tool this covers the essentials: what is produced, who acts next, and that no PII is involved. With no output schema, a brief note on what the call returns (a URL string) would close the last gap.

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 description coverage is 100% and both optional parameters are already labeled as attribution-only in the schema. The description adds nothing about parameters, so the baseline 3 applies; it neither compensates nor detracts.

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?

States a specific verb and resource (create a single-use Calendly link) plus scope qualifiers: free, 30-minute, consultation with IRM. An agent can immediately tell this apart from check_availability or get_pricing, which do not mint links.

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

Usage Guidelines4/5

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

The description gives clear context for use — hand the link to a person so they can pick a time and confirm on Calendly — and explicitly scopes out booking behavior ("This tool books nothing itself"). It stops short of naming a sibling as the alternative when a user wants to see times first, so no explicit when-not guidance.

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