Skip to main content
Glama

save_event_draft

Idempotent

Create or update an unpublished event. Use revision 0 to create and the current revision to edit. Ticket amounts are minor units in the specified currency.

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": {
      "event": "<event>",
      "idempotencyKey": "<idempotencyKey>"
    },
    "name": "save_event_draft"
  }
}

Input Schema

NameRequiredDescriptionDefault
eventYes
idempotencyKeyYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.7/5.0
Behavior3/5

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

The annotations already declare non-read-only, idempotent, non-destructive, closed-world behavior, and the description adds useful context the annotations do not: the event stays 'unpublished', revision acts as an optimistic-concurrency token, and ticket amounts are minor units. It does not disclose what happens on a stale revision, whether drafts are visible to others, or what permissions are needed.

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 short sentences, front-loaded with the action, then the create/edit rule, then the unit convention. Nothing is redundant and no sentence is filler.

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?

For a nested, mutation tool with no output schema and 0% documented schema fields, the definition covers the two most confusing concepts (revision and minor units) but omits idempotency key usage, required-field expectations, and the failure mode for a revision conflict. Adequate but with clear gaps.

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 0% and there are roughly a dozen nested event fields, so the description has to carry the load. It clarifies revision semantics and the ticketAmount/ticketCurrency units, but leaves idempotencyKey, timeZone, startsAt/endsAt epoch representation, and capacity constraints unexplained.

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?

The opening sentence gives a specific verb pair and resource ('Create or update an unpublished event'), and the second sentence clarifies the two modes via the revision value. It is immediately distinguishable from sibling read tools like get_event or mutation tools like void_event_ticket, though it never explicitly names an alternative.

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?

The guidance 'Use revision 0 to create and the current revision to edit' is a concrete rule that tells the agent which mode it is entering and what value selects it. It stops short of stating when this tool should not be used (e.g., for published events) or pointing to other event tools.

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