Skip to main content
Glama

create_event

Create a new event (initially DRAFT unless status is specified) for the active company.

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

Input Schema

NameRequiredDescriptionDefault
nameYesEvent title
endDateNoISO end date/time
locationNoVenue name
startDateNoISO start date/time
visibilityNoEvent visibility
descriptionNoEvent description or introduction
ticketPriceNoTicket price in major currency units (0 for free)
deliveryModeNoDelivery format
venueAddressNoStreet address of the venue

Output Schema

NameRequiredDescriptionDefault
dataYesTool result payload — shape varies per tool, see the tool description
summaryYesOne-line human-readable summary of the action
renderTypeYesUI rendering hint for the result

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare this is a non-read-only, non-destructive, non-idempotent write. The description adds genuinely useful context beyond that: new events default to DRAFT and are scoped to the active company. It omits other behavior an agent would want — duplicate creation risk implied by idempotentHint=false, permission requirements, and validation failures — and mentions a "status" input that does not exist in the schema.

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?

A single front-loaded sentence with the create action first and the default-state caveat in parentheses — efficient and easy to scan. The parenthetical about "status" is the one phrase that does not earn its place, since no such parameter exists.

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?

The schema fully specifies all nine parameters, an output schema exists, and annotations cover the safety profile, so the description's remaining job is scope and default behavior, both of which it states. Only minor gaps (permissions, duplicate behavior) remain, which is acceptable given the structured coverage.

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%, so the schema already documents all nine parameters including the two enums, which sets the baseline at 3. The description adds only the DRAFT-default rule, and the referenced "status" field has no corresponding schema property, so it contributes little usable parameter meaning.

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 new event") plus the resulting initial state, which clearly distinguishes it from siblings such as create_booking or create_campaign. It stops short of explicitly contrasting with any named alternative, so it lands just below the top band.

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?

There is no when-to-use / when-not-to-use guidance and no mention of prerequisites such as company context or required fields. The only implied guidance is that events belong to the "active company," which an agent must infer from a scoping phrase rather than a stated rule.

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.