Skip to main content
Glama
Sign In
brief-mcp

brief-mcp

by MLDreamer
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Get Upcoming Meetings

get_upcoming_meetings

Retrieve upcoming Google Calendar meetings for the next N hours, including titles, times, attendees, and meeting links to support meeting preparation.

Instructions

Get upcoming meetings from Google Calendar for the next N hours.

Returns a list of meeting objects with:

  • id, title, start_time, end_time (ISO format)

  • attendees (name + email)

  • meeting_url (Google Meet / Zoom / Teams link if present)

  • location, description

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_upcoming_meetings"
  }
}

Input Schema

NameRequiredDescriptionDefault
hours_aheadNoHow many hours into the future to look (default: 24).

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.0

TDQS

A3.7/5.0
Behavior3/5

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

With no annotations, the description carries the full behavioral burden. It discloses the data source and the forward-looking window, which is useful, but says nothing about whose calendar is read, auth requirements, timezone basis, or empty-result behavior.

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 purpose is front-loaded in one tight sentence. The follow-on return-field list is slightly redundant given an output schema exists, but it is compact and well-structured.

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 simple read tool with one optional parameter and an existing output schema, the description covers purpose and scope adequately. Only timezone/auth context is absent, which is a minor gap.

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% and the single optional hours_ahead parameter is documented with its default in the schema. The description only restates 'next N hours' and adds no format or boundary detail beyond that baseline.

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?

States a specific verb (Get), resource (upcoming meetings), and source (Google Calendar) with an explicit time scope (next N hours). This cleanly separates it from the sibling get_outlook_meetings, which covers a different provider.

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 'from Google Calendar' qualifier implicitly routes the agent away from get_outlook_meetings, but there is no explicit when-to-use statement, no mention of when to prefer search_meeting_history or get_meeting_brief, and no stated prerequisites.

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