Skip to main content
Glama

dismiss_calendly_unmatched_booking

Destructive

Hide an unmatched Calendly booking from the list (the booking itself stays in Calendly). (confirm-gated: previews until confirm: true)

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": {
      "id": "<id>"
    },
    "name": "dismiss_calendly_unmatched_booking"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYes
confirmNoMust be true to actually execute. If false/omitted, returns a preview only.

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?

Annotations declare destructiveHint=true and readOnlyHint=false, which alone would suggest data loss; the description usefully refines that by clarifying the underlying Calendly booking is untouched and only the local list entry is hidden. It also restates the confirm-gate behavior (preview until confirm: true), which is already in the schema but reinforces the two-phase execution model. It does not describe permissions required or whether the hide is reversible.

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?

Two short sentences with the action and its scope front-loaded, then the confirm-gate caveat. Every clause carries information, though the stacked parentheticals make it slightly less scannable than it could be.

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-parameter, single-object mutation with a confirm gate and no output schema, the definition covers the key facts: what is hidden, what is not affected, and that execution requires confirm: true. Minor gaps remain — what a preview response looks like and behavior for an unknown id — but nothing an agent needs to invoke it correctly is absent.

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 50%: 'confirm' is fully documented in the schema, while 'id' has no schema description. The description indirectly establishes that 'id' identifies an unmatched Calendly booking, which is the only compensation offered — no format, source, or validation guidance for the id is added.

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?

States a specific verb and resource: 'Hide an unmatched Calendly booking from the list'. The parenthetical '(the booking itself stays in Calendly)' precisely bounds the scope of the action, and 'from the list' implicitly points at the sibling list_calendly_unmatched_bookings, though no sibling is named explicitly.

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?

Usage is implied by the verb and object — call this when you have an unmatched booking you want to remove from the visible list — but there is no explicit when-not guidance, no stated prerequisites (e.g., that the booking must first appear in the unmatched list), and no named alternative to use instead for other cleanup cases.

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.