Skip to main content
Glama

Coline

Create event template

create_event_template

Saves an event template: a title, length, attendees, call and reminders to start new events from.

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": {
      "workspace": "<workspace>",
      "name": "<name>",
      "payload": "<payload>"
    },
    "name": "create_event_template"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYes
payloadYes
workspaceYesWorkspace slug from workspaces.list, e.g. "acme".

Output Schema

NameRequiredDescriptionDefault
templateYes

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false, idempotentHint=false and openWorldHint=false, so the safety profile is covered. The description adds the useful framing that the result is a reusable template, but is silent on permission requirements, duplicate-name behavior, and whether a template can be edited after creation.

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?

One compact sentence, front-loaded with the write action and immediately followed by the template's contents. No filler or repetition.

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

Completeness3/5

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

An output schema exists, so return values need not be explained. However, for a create-mutation whose payload is a large nested object with many optional fields (recurrence, meeting settings, visibility, travel time), the description covers only the headline fields and leaves the agent to read the schema for the rest.

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 only 33% (workspace is the sole described parameter), so the description must compensate. It does map several payload concepts (length=durationMinutes, attendees, call, reminders), but never clarifies the required top-level `name` versus `payload.title`, nor mentions recurrence, visibility, location, or travel fields.

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?

Uses a specific verb plus resource ("Saves an event template") and enumerates the template's contents: title, length, attendees, call, reminders. The phrase "to start new events from" distinguishes it in spirit from create_event, but it never names a sibling explicitly.

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 purpose statement implies the when: build a reusable template rather than a one-off event. There is no explicit guidance on when not to use it, nor any pointer to update_event_template or list_event_templates for the modify/read paths.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources