Fetches the authenticated Calendly user profile via Personal Access Token or CALENDLY_API_KEY, enabling agents to verify account identity before scheduling workflows.
Get the authenticated Calendly user profile.
| Name | Required | Description | Default |
|---|---|---|---|
| api_key | No | Calendly Personal Access Token (or set CALENDLY_API_KEY) |
Changes observed during successful MCP inspections.
v0.1.9v0.1.5Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already establish that this is a safe, read-only, idempotent operation. The description adds useful authentication context by specifying that it returns the authenticated user's profile, though it does not describe rate limits or response fields.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
A single sentence with no wasted words, and the key qualifier "authenticated" is front-loaded. It is appropriately sized for a simple profile lookup.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a low-complexity read-only tool with rich annotations and fully described auth input, the description is sufficient. It could mention the profile fields returned, but the operation is otherwise clear.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The single api_key parameter is fully documented in the schema, including the environment-variable fallback. The description adds no parameter guidance beyond the schema, which is acceptable at 100% schema coverage.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
States a specific verb and resource: get the authenticated Calendly user profile. This clearly distinguishes it from sibling tools such as list_calendly_event_types and get_calendly_event.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The phrase "authenticated Calendly user profile" makes the intended context clear: retrieve the current user's own profile. It does not explicitly discuss alternatives or exclusions, but none are necessary for this narrow operation.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.