Ignix

Add a task or meeting

create_agenda_item

Add a task (something to do by a date, e.g. telling a creator how to film some scenes) or a meeting (optionally weekly) to the agenda. The people in assigneeIds get a reminder by push or email N days before. A meeting in a workspace with Google Calendar connected is created there too, with a Meet room if meet is true, and the assignees get the invitation by email. Confirm the details with the user first: it notifies real people.

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": {
      "kind": "<kind>",
      "title": "<title>",
      "start": "<start>"
    },
    "name": "create_agenda_item"
  }
}

Input Schema

Name	Required	Description
`kind`	Yes	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`	Yes	"YYYY-MM-DD HH:MM": the due date of a task or the start of a meeting, in `timeZone`.
`title`	Yes	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

A4.3/5.0

Behavior5/5

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

Annotations only declare it is a non-read-only, open-world, non-destructive write. The description adds the substance an agent actually needs: reminders go out by push or email N days before, a Google Calendar event and Meet room may be created, invitations are emailed to assignees, and real people are notified. That is exactly the side-effect disclosure a mutation tool needs.

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?

Four sentences, front-loaded with the core action, then side effects, then the user-confirmation warning. The parenthetical example ("telling a creator how to film some scenes") is slightly verbose but genuinely aids disambiguation of task vs meeting.

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 13-parameter creation tool with no output schema, the description covers the branching behavior (task vs meeting, calendar, Meet, weekly repeat, reminders) and the user-confirmation requirement. It does not say what comes back (e.g. the new item's id) or address durationMin/location, but the schema carries those at full 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 coverage is 100%, so every parameter is already documented, including the enum meanings and the idempotencyKey retry contract. The description reinforces a few semantics (assigneeIds drive reminders and invitations, meet requires Calendar) but adds little beyond the schema text, so the baseline of 3 is right.

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

Purpose5/5

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

The description opens with a specific verb and resource ("Add a task ... or a meeting ... to the agenda") and immediately disambiguates the two kinds with concrete definitions, so an agent can tell exactly what gets created and which of the two modes applies.

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?

It gives a real precondition — "Confirm the details with the user first: it notifies real people" — plus the conditions that activate extras (Google Calendar connected, meet=true, repeatWeekly). It stops short of naming when to prefer update_agenda_item or create_appointment instead, so routing between write-siblings is left to inference.

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?