Skip to main content
Glama
Sign In
Microsoft Events MCP Server

Microsoft Events MCP Server

by trsdn
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

get_event_details

Retrieve detailed information about a specific Microsoft event using its event ID. Access schedule, speakers, and venue from search results.

Instructions

Get details for a specific event by its ID.

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": {
      "event_id": "<event_id>"
    },
    "name": "get_event_details"
  }
}

Input Schema

NameRequiredDescriptionDefault
localeNoAPI locale (default: de-de).de-de
event_idYesThe event ID (from search_events results).

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/5.0
Behavior2/5

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

No annotations are provided, so the description must carry behavioral disclosure. It only states 'Get details,' which implies a read operation, but it doesn't disclose any potential errors, permissions, rate limits, or scope of returned details. The description adds little beyond the tool name.

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?

One sentence of 9 words, front-loaded with the core action. No wasted words.

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?

The tool is simple (get by ID), the schema fully documents parameters, and an output schema exists to explain return values. However, the lack of any usage guidance relative to siblings or any behavioral caveats leaves the description slightly under-specified, though adequate for a basic read operation.

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 description coverage is 100%, with both event_id and locale having descriptions. The description's phrase 'by its ID' generally maps to event_id but adds no additional meaning beyond the schema.

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?

The description uses a specific verb ('Get') and identifies the resource ('details for a specific event') and the unique accessor ('by its ID'). This distinguishes it from sibling tools like search_events (searching) and get_event_stats (statistics).

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?

The description gives no explicit when-to-use or alternative guidance. However, the event_id parameter in the schema references 'from search_events results,' implying usage after searching. This is implied rather than stated.

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