Conecto

Add a Google Calendar event

google_calendar_create

Put an event in a mailbox's calendar and invite its attendees, with a Google Meet link when asked. Times with an offset, or local to timezone. $0.001. Costs $0.001 per call; nothing if it fails.

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": {
      "subject": "<subject>",
      "start": "<start>",
      "end": "<end>"
    },
    "name": "google_calendar_create"
  }
}

Input Schema

Name	Required	Description
`end`	Yes
`body`	No
`start`	Yes
`mailbox`	No	One of the mailboxes the agent may act as; optional when only one is connected.
`subject`	Yes
`location`	No
`timezone`	No
`attendees`	No
`online_meeting`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 28, 2026

TDQS

B3.2/5.0

Behavior3/5

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

Annotations already declare mutation, non-idempotency and non-destructive behavior, so the bar is lower. The description adds real value with pricing ('$0.001 per call; nothing if it fails') and the fact that attendees are invited and a Meet link is created, but it omits whether invitees receive email notifications, auth connection requirements, and duplicate-event 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?

Front-loaded with the core action, short and mostly waste-free. Minor redundancy: cost appears twice ('$0.001' and then 'Costs $0.001 per call; nothing if it fails').

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 9-parameter mutation with no output schema and thin schema descriptions, the essentials (action, time handling, Meet link, cost) are covered. Missing prerequisites and the shape of the created event keep it from full completeness.

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 only 11% (just `mailbox`), and 9 parameters exist, so the description must compensate. It clarifies time format ('with an offset, or local to `timezone`') and ties `online_meeting` to Meet links, but leaves `body`, `location`, `attendees` format, and start/end syntax undocumented.

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+resource (put an event in a mailbox's calendar) plus the two notable optional behaviors: inviting attendees and adding a Google Meet link. It is clearly distinguishable from google_calendar_events (list) and google_calendar_cancel, though those siblings are 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 Guidelines2/5

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

No statement of when to use this versus google_calendar_events, google_calendar_cancel, or m365_calendar_create for Microsoft mailboxes. The 'when asked' phrasing for Meet links is the only conditional guidance, and prerequisites like google_connect or mailbox selection are never mentioned.

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

All Conecto tools Inspect

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

Need Help?