Skip to main content
Glama
ktibbs9417

GAM MCP Server

by ktibbs9417
OverviewSchemaRelated ServersScoreDiscussions
Python
Local

transfer_calendar_event

Transfer a calendar event to a new organizer by updating the organizer field and adding the destination user as an organizer-level attendee. Requires confirmation to execute.

Instructions

    Transfers a calendar event from one user to another.
    Note: GAM7 v7.31.03+ removed the direct calendar transfer command
    due to Calendar API changes. This tool will update the event's organizer field
    and add the destination user as an organizer-level attendee.
    
    WARNING: The Meet link may break if the original organizer leaves the org.
    
    Args:
        source_user_email: The original organizer of the event.
        destination_user_email: The new organizer for the event.
        event_id: The ID of the calendar event.
        confirmed: Must be True to execute. If False, returns a preview.
        
    GAM pattern:
        gam calendar <source_user_email> update event id <event_id>
            organizer <destination_user_email>

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
event_idYes
confirmedNo
source_user_emailYes
destination_user_emailYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Tool Definition Quality

A4.3/5.0
Behavior4/5

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

Discloses that the tool updates the organizer field, adds destination as organizer-level attendee, and requires confirmed=true to execute (preview otherwise). Warns about Meet link breakage. No annotations to contradict.

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?

Description is well-structured with purpose, note, warning, arguments list, and GAM pattern. No redundant sentences. Could be slightly more compact, but each section adds necessary context.

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?

Covers core functionality, warnings, and parameter semantics. Output schema exists, so return values are not needed. Adequate for a four-parameter tool with no complex nested objects.

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?

Adds value beyond schema: explains confirmed parameter behavior (must be true to execute, false returns preview). Schema has no descriptions, so this explanation is essential for correct invocation. Other parameters are clear from names.

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?

Clearly states the action (transfers) and resource (calendar event). Distinguishes from sibling tools which are audit, permission, and user management tools. No ambiguity.

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?

Provides context about API changes and the tool's approach. Includes a GAM pattern and a warning about Meet link breakage. Lacks explicit when-to-use vs alternatives, but sufficient for decision-making.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/ktibbs9417/gamcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server