Skip to main content
Glama

Coline

Update event template

update_event_template
Idempotent

Renames an event template or changes what it fills in.

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>",
      "templateId": "<templateId>"
    },
    "name": "update_event_template"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNo
payloadNo
workspaceYesWorkspace slug from workspaces.list, e.g. "acme".
templateIdYesTemplate id from list_event_templates.
sortPositionNo

Output Schema

NameRequiredDescriptionDefault
templateYes

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

C2.4/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=false, idempotentHint=true, and destructiveHint=false, so the safety profile is covered structurally. The description adds nothing beyond that: it does not say whether omitted payload fields are preserved or cleared (crucial for a nested payload with ~20 optional properties), nor that updates require prior template existence in the workspace.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

It is a single short sentence with no wasted clauses, but the brevity comes from under-specification rather than discipline. The only measurable behavior is front-loaded, yet it conveys too little to act on.

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

Completeness2/5

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

For a mutation tool with a large nested payload, 5 parameters, and several update-related siblings, one vague sentence is far from sufficient. The existence of an output schema removes the need to describe return values, but the update semantics and payload scope remain unexplained.

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

Parameters2/5

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

Schema description coverage is only 40% across 5 parameters, so the description needs to compensate and does not. It hints at `name` and `payload` but says nothing about `workspace`, `templateId`, or `sortPosition`, and gives no guidance on partial payload semantics for the deeply nested recurrence/attendee/meetingSettings objects.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

"Renames an event template or changes what it fills in" identifies the resource (event template) and a loose set of operations, but the phrase "what it fills in" is informal and does not clearly map to the `payload` field an agent must construct. It distinguishes the tool from create/delete siblings in spirit, but does not distinguish it from update_event.

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 indication of when to use this instead of `update_event`, `create_event_template`, or when a template should be edited versus recreated. No prerequisites, no note that the template must already exist, and no exclusions are given.

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