Skip to main content
Glama
Sign In

PineBill

by app.pinebill
OverviewDiscussionsAdmin

Create calendar event

create_calendar_event

Create a calendar event, such as a client meeting or a reminder. Times without an offset are in the organization's timezone. For an all-day event set allDay and pass dates (YYYY-MM-DD); use the same date for start and end for a single day.

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": {
      "title": "<title>",
      "startDate": "<startDate>",
      "endDate": "<endDate>"
    },
    "name": "create_calendar_event"
  }
}

Input Schema

NameRequiredDescriptionDefault
colorNoHex color like #2563eb
titleYesEvent title
allDayNoAll-day event (default false)
endDateYesEnd (ISO date-time); must be on or after the start
locationNoWhere it happens, or a meeting link
startDateYesStart (ISO date-time, or ISO date for all-day events)
descriptionNoNotes

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

A3.9/5.0
Behavior3/5

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

Annotations already declare non-read-only, non-destructive, non-idempotent, closed-world behavior, so the bar is lower. The description usefully adds timezone defaulting and all-day mechanics, but does not address what a non-idempotent create means in practice (duplicate events on retry) or any side effects such as notifications to attendees.

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?

Three tight sentences with no filler; the core action comes first, followed by the two behavioral clarifications that actually affect how the call is built.

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 7-parameter create tool with full schema coverage, annotations, and no output schema, the description covers the semantics an agent would most likely get wrong (timezone, all-day handling). It does not mention return value or duplicate-creation risk, a minor gap given the non-idempotent hint and absence of an output schema.

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

Parameters4/5

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

Schema coverage is 100%, so baseline is 3, and the description goes beyond it: it explains how to interpret offsets in date-times and the exact recipe for all-day events (set allDay, pass YYYY-MM-DD, same date for start and end). It leaves color, location, and description to the schema, which is reasonable.

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 ('Create a calendar event') and grounds it with concrete examples (client meeting, reminder). The verb alone separates it from the delete_calendar_event and update_calendar_event siblings, though no sibling is named explicitly.

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

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives clear in-context guidance for the tricky cases: offset-less times are organization timezone, and all-day events require allDay plus dates with the same date for start/end. There are no exclusions or pointers to alternatives (e.g., when to use update_calendar_event instead), but the positive conditions are explicit.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All PineBill toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources