Skip to main content
Glama
Sign In
SavvyCal MCP Server

SavvyCal MCP Server

by OfirOhan
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Get meeting

get_event
Read-only

Fetch one meeting by event ID to view attendees, conferencing details, and submitted form answers.

Instructions

Get one meeting with attendees, conferencing details and form answers.

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": {
      "eventId": "<eventId>"
    },
    "name": "get_event"
  }
}

Input Schema

NameRequiredDescriptionDefault
eventIdYesEvent ID or UUID (from list_events)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint, so the safety profile is covered. The description adds real value by disclosing what the response contains (attendees, conferencing details, form answers), which matters since there is no output schema. It does not mention error behavior for an unknown eventId.

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, front-loaded with the verb and resource, with the return contents appended for efficiency. Nothing redundant or padded.

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 single-resource read with full schema coverage and read-only annotations, this covers what the agent needs; and with no output schema, naming the returned fields is a genuine addition. Only missing detail is failure behavior on a missing/invalid ID.

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 eventId parameter is documented as "Event ID or UUID (from list_events)". The description adds no format or sourcing detail beyond that, so the schema does all the work — the baseline 3 applies.

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

Purpose4/5

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

States a specific verb and resource ("Get one meeting") and enumerates the payload (attendees, conferencing details, form answers). The singular "one meeting" implicitly separates it from the list_events sibling, though that sibling is never named.

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?

Usage is only implied: an agent can infer this is the by-ID lookup for a single meeting, and the schema's "from list_events" hints at the workflow. No explicit when-to-use, prerequisites, or alternatives (list_events, find_available_slots) are 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