Skip to main content
Glama

update_event

Modify event details in Microsoft Calendar via Microsoft MCP server. Input event ID, account ID, and desired updates to adjust properties such as time, location, or description.

Instructions

Update event properties

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
account_idYes
event_idYes
updatesYes

Implementation Reference

  • The core handler function for the 'update_event' tool. It formats the updates dictionary according to Microsoft Graph API requirements and sends a PATCH request to update the specified event. Registered via the @mcp.tool decorator.
    @mcp.tool
    def update_event(
        event_id: str, updates: dict[str, Any], account_id: str
    ) -> dict[str, Any]:
        """Update event properties"""
        formatted_updates = {}
    
        if "subject" in updates:
            formatted_updates["subject"] = updates["subject"]
        if "start" in updates:
            formatted_updates["start"] = {
                "dateTime": updates["start"],
                "timeZone": updates.get("timezone", "UTC"),
            }
        if "end" in updates:
            formatted_updates["end"] = {
                "dateTime": updates["end"],
                "timeZone": updates.get("timezone", "UTC"),
            }
        if "location" in updates:
            formatted_updates["location"] = {"displayName": updates["location"]}
        if "body" in updates:
            formatted_updates["body"] = {"contentType": "Text", "content": updates["body"]}
    
        result = graph.request(
            "PATCH", f"/me/events/{event_id}", account_id, json=formatted_updates
        )
        return result or {"status": "updated"}
  • The @mcp.tool decorator registers the update_event function as an MCP tool with FastMCP instance 'mcp'.
    @mcp.tool
Behavior1/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. 'Update event properties' implies a mutation operation but reveals nothing about required permissions, whether changes are reversible, rate limits, error conditions, or what the response contains. For a 3-parameter mutation tool with zero annotation coverage, this is a critical gap that leaves the agent guessing about important behavioral traits.

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?

The description is maximally concise at three words with zero wasted language. It's front-loaded with the core action and resource. While severely under-specified, it achieves perfect conciseness for what it does communicate.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness1/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given a mutation tool with 3 parameters (including a nested object), 0% schema description coverage, no annotations, and no output schema, the description is completely inadequate. It provides only the most basic purpose statement without addressing parameter meanings, behavioral expectations, usage context, or return values. The agent would struggle to use this tool correctly without additional documentation or trial-and-error.

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

Parameters1/5

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

The schema description coverage is 0%, meaning none of the three parameters (account_id, event_id, updates) have descriptions in the schema. The description 'Update event properties' adds no meaningful information about these parameters beyond what's implied by their names. It doesn't explain what 'updates' object should contain, what formats are expected for IDs, or any constraints. The description fails to compensate for the complete lack of schema documentation.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose2/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description 'Update event properties' is a tautology that essentially restates the tool name 'update_event'. While it indicates a mutation operation on events, it lacks specificity about what kind of properties can be updated or the scope of the operation. It doesn't distinguish this tool from its sibling 'update_contact', 'update_email', or 'update_file' beyond the resource type.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines1/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides no guidance on when to use this tool versus alternatives. It doesn't mention prerequisites (e.g., needing an existing event), when not to use it, or how it differs from related tools like 'create_event', 'delete_event', 'get_event', or 'respond_event'. The agent must infer usage entirely from the tool name and context.

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

Related 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/elyxlz/microsoft-mcp'

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