Ignix

Change a task or meeting

update_agenda_item

DestructiveIdempotent

Change a task or meeting by id (from list_agenda): only what you pass changes. done=true marks a task as done (and stops its reminder); on a weekly task, only the next time. If it is in Google Calendar, the event is updated and the attendees are told.

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

Input Schema

Name	Required	Description
`id`	Yes
`done`	No	Mark as done / not done.
`kind`	No	task = something to do by a date (e.g. "film 3 scenes in natural light"); meeting = a call at a time.
`meet`	No	Meeting only: create a Google Meet room. Needs Google Calendar connected in Appointments for that workspace.
`notes`	No	Details: what to film and how, the agenda of the meeting…
`start`	No	"YYYY-MM-DD HH:MM": the due date of a task or the start of a meeting, in `timeZone`.
`title`	No	Up to 200 characters.
`location`	No	Meeting only: a video call link of their own (Zoom, Teams…) when it is not Meet.
`timeZone`	No	IANA zone the start is written in, e.g. "Europe/Moscow". Defaults to the organization time zone (where it is shown).
`assigneeIds`	No	Member user ids it is for (from list_team). They get the reminder, and the Google invitation for a meeting.
`durationMin`	No	Meeting length in minutes (5-600). Default 30.
`workspaceId`	No	The client it is about. Defaults to the workspace this connection is scoped to.
`repeatWeekly`	No	Repeats every week at the same day and time (a weekly meeting).
`idempotencyKey`	No	Optional. A unique id for this action (16-128 chars: letters, digits, _ : . -). If you are unsure whether a call went through (timeout, network error), repeat it with the SAME idempotencyKey and the same arguments: you get the original result and nothing is done twice.
`remindDaysBefore`	No	Reminder N days before (by push or email, per person settings); 0 = same day, 2 hours before; null = none. Default 1.

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 9, 2026

TDQS

A3.7/5.0

Behavior3/5

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

Annotations already declare destructiveHint=true, idempotentHint=true and openWorldHint=true, so the safety profile is largely covered. The description adds real value by disclosing the side effect that Google Calendar events are updated and attendees notified, but it says nothing about failure modes, permission requirements, or what is destroyed by a change.

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 mutation scope, then conditional semantics, then external side effects. No filler and nothing buried.

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 15-parameter mutation tool with 93% schema coverage, the description covers the highest-risk ambiguities (partial update, done semantics, recurrence, Calendar notification). Remaining gaps, such as kind switching and error behavior on an invalid id, are modest.

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

Parameters4/5

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

Goes beyond the already-rich schema by explaining the meaning of done=true (stops the reminder; on a weekly task only the next occurrence) and the external consequence of a Calendar-linked item. It does not cover the trickier interactions, such as what happens when kind is switched or how start/timeZone/repeatWeekly combine.

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 ("Change a task or meeting by id") and adds the crucial partial-update rule ("only what you pass changes"), which distinguishes it from create/delete siblings. It also names list_agenda as the id source, though it does not explicitly contrast with create_agenda_item or delete_agenda_item.

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?

Gives useful context on how to call it (supply only the fields to change, id from list_agenda) but offers no when-not guidance or explicit routing to alternatives such as create_agenda_item when the item does not yet exist.

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

All Ignix 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?