Skip to main content
Glama
Sign In
shipmail-mcp

shipmail-mcp

by shipmail-to
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Get Calendar Event

shipmail_get_calendar_event
Read-only

Fetch a calendar event by its ID from a specified mailbox address.

Instructions

Fetch one calendar event by ID for a mailbox.

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": {
      "id": "<id>",
      "mailbox": "<mailbox>"
    },
    "name": "shipmail_get_calendar_event"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesCalendar event ID.
mailboxYesThe mailbox (calendar owner) address.

Output Schema

NameRequiredDescriptionDefault
eventYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.1.10

TDQS

A3.7/5.0
Behavior3/5

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

The description is consistent with annotations (readOnlyHint=true). However, it adds no behavioral detail beyond the annotations, which already indicate a safe read operation.

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?

Single sentence, no wasted words. Essential information is front-loaded.

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

Completeness5/5

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

For a simple get-by-ID operation, the description is complete. Output schema exists, so return value details are covered elsewhere.

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 coverage is 100%, and parameter descriptions in the schema are clear. The tool description does not add any additional meaning beyond what the schema already provides.

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 clearly states the action (fetch), resource (calendar event), and scope (by ID for a mailbox). It distinguishes from sibling tools like list_calendar_events or create_calendar_event.

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?

No guidance on when to use this tool versus alternatives (e.g., list_calendar_events for multiple events). The description lacks usage context or preconditions.

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