Skip to main content
Glama

get_event

Retrieve comprehensive event details from the Microsoft MCP server by specifying event and account IDs, enabling efficient management of calendar entries and scheduling tasks.

Instructions

Get full event details

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
account_idYes
event_idYes

Implementation Reference

  • The main handler function for the 'get_event' tool, decorated with @mcp.tool for automatic registration in FastMCP. It retrieves full details of a specific calendar event using the Microsoft Graph API.
    @mcp.tool
    def get_event(event_id: str, account_id: str) -> dict[str, Any]:
        """Get full event details"""
        result = graph.request("GET", f"/me/events/{event_id}", account_id)
        if not result:
            raise ValueError(f"Event with ID {event_id} not found")
        return result
Behavior2/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. 'Get full event details' implies a read-only operation, but it doesn't specify whether this requires authentication, has rate limits, returns structured data, or handles errors. For a tool with zero annotation coverage, this leaves critical behavioral traits unaddressed.

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 extremely concise with just three words, front-loading the core action and resource. There's no wasted language, making it easy to parse quickly, though this brevity contributes to gaps in other dimensions like guidelines and transparency.

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

Completeness2/5

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

Given the complexity of retrieving event details with two required parameters, no annotations, and no output schema, the description is incomplete. It doesn't explain the return format, error handling, or dependencies, leaving the agent with insufficient context to use the tool effectively beyond basic parameter passing.

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

Parameters2/5

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

Schema description coverage is 0%, meaning the input schema provides no descriptions for the two parameters (account_id and event_id). The description adds no meaning beyond what the schema's titles imply, failing to explain what these IDs represent, how to obtain them, or their format, which is insufficient given the low coverage.

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

Purpose3/5

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

The description 'Get full event details' states the verb ('Get') and resource ('event details'), which clarifies the tool's basic purpose. However, it's vague about what constitutes 'full details' and doesn't distinguish it from sibling tools like 'list_events' or 'search_events', which also retrieve event information but with different scopes or filters.

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

Usage Guidelines2/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 like 'list_events' or 'search_events'. It lacks explicit instructions on prerequisites (e.g., needing an account_id and event_id) or context for when this retrieval is appropriate, leaving the agent to infer usage from the tool name and parameters alone.

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