Skip to main content
Glama
ghl-mcp-server-v2

ghl-mcp-server-v2

by zackscriven

ghl_calendar_group_update_status

Idempotent

Toggles a calendar group's active status by setting isActive true or false, enabling you to disable or re-enable the group.

Instructions

Despite the underlying 'disable-group' operation name, the required body field isActive (boolean) toggles both directions — set isActive:true to re-enable the group. Disable Group Endpoint: PUT /calendars/groups/{groupId}/status (Version header: v3; source: v3/calendars-v3.json) OAuth scopes: calendars/groups.write

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": {
      "groupId": "<groupId>",
      "body": "<body>"
    },
    "name": "ghl_calendar_group_update_status"
  }
}

Input Schema

NameRequiredDescriptionDefault
bodyYesRequest body (schema carried verbatim from the official OpenAPI spec).
groupIdYesGroup Id

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv2.1.0
    • addedInput schema / properties / body / title
      Added value: +"GroupStatusUpdateParams"
  2. First observedv2.0.0

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare idempotentHint=true, destructiveHint=false, and openWorldHint=true, so the safety profile is covered. The description adds genuinely new context: the endpoint, the required v3 version header, and the OAuth scope (calendars/groups.write), which tells the agent what authorization is needed. The toggle clarification further sharpens behavior beyond annotations.

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?

The most important clarification (both-direction toggle) is front-loaded, followed by compact endpoint/scope metadata. It is appropriately sized for a two-parameter tool. Minor fragmentation from restating the 'Disable Group' title inline keeps it from a 5.

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-param toggle with no output schema and rich annotations, the description covers the decisive semantic (bidirectional toggle), plus endpoint, version, and scope. An agent has enough to invoke it correctly; only the sibling-relationship guidance is missing.

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?

Schema coverage is 100%, so the baseline is 3, but the description adds real meaning the schema lacks: the schema only says 'Is Active?', while the description explains that isActive toggles both directions and that true re-enables. That resolves the core ambiguity for the primary parameter.

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?

The description states a specific operation — toggling a calendar group's active status via isActive — and proactively resolves the misleading 'disable-group' operation name by explaining it works in both directions. It does not explicitly name or differentiate from the sibling ghl_calendar_group_update, which prevents a 5.

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?

It gives clear direction-level guidance ('set isActive:true to re-enable the group'), which tells the agent how to use the toggle correctly. However, it never addresses when to use this tool versus alternatives like ghl_calendar_group_update or ghl_calendar_group_delete, leaving tool selection to inference.

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