Skip to main content
Glama

list_calendly_unmatched_bookings

Read-only

Calendly bookings whose invitee email didn't match any client, so no session was created. Invite or add the person, or dismiss the booking.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.7/5.0
Behavior3/5

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

Annotations already establish readOnlyHint=true and openWorldHint=false, so the safety profile is covered elsewhere. The description adds genuinely useful provenance: these are bookings that produced no session because matching failed, which tells the agent why the data exists in this state. It does not cover ordering, pagination, or whether the list persists until dismissed.

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?

Two short sentences: the first defines the data set, the second gives the available actions. The identifying condition (unmatched invitee email) is front-loaded and no words are wasted.

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 parameterless read tool with no output schema, an agent knows what the results are and what can be done with them. Minor gap: no hint about what fields each booking row carries, which matters slightly since there is no output schema to fall back on.

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

Parameters4/5

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

The tool takes zero parameters, so there is nothing for the description to disambiguate and the baseline applies. Schema coverage is nominally 100% on an empty object, so no compensation is needed.

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?

Defines the exact resource: Calendly bookings whose invitee email matched no client, with the causal consequence that no session was created. That is far more specific than a bare 'list unmatched bookings' and clearly separates it from the sibling dismiss_calendly_unmatched_booking. It loses a point only because the verb 'list' is implied by the name rather than stated in the description.

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 sentence 'Invite or add the person, or dismiss the booking' tells the agent what to do with the results, which implicitly signals this is a triage/queue tool rather than a general booking list. However, it never states when to reach for this versus get_calendly_status or another listing tool, and offers no prerequisites or exclusions.

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.