AI Team OS

Overview Schema Source Related Servers Discussions Admin

meeting_update

Update a meeting's topic or participant list. Notes are accepted but not stored; use meeting_conclude to mark a meeting as concluded.

Instructions

Update a meeting's topic or participant list.

notes is accepted but not stored (meetings have no notes field) and the call still reports success; conclusions go on the task wall (task_create / task_update). Changing participants does not change the attendance list meeting_create recorded. To mark a meeting concluded, use meeting_conclude.

Input Schema

TableJSON Schema

Name	Required	Description
`notes`	No	Accepted but not stored (meetings have no notes field)
`topic`	No	New topic text (optional)
`meeting_id`	Yes	Meeting ID (required)
`participants`	No	Updated participant list (optional)

Output Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedv1.15.0Sep 30, 2026

changedInput schema / properties / notes / description

Previous value: -"Meeting notes or conclusion summary to store (optional)"New value: +"Accepted but not stored (meetings have no notes field)"

First observedv1.9.0Jul 14, 2026

TDQS

A4.9/5.0

Behavior5/5

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

With no annotations, the description carries the full behavioral burden and discloses two non-obvious gotchas: accepting notes without storing them while still reporting success, and changing participants without altering the attendance list recorded at creation. It also names the correct alternative for marking a meeting concluded.

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?

The purpose is front-loaded in the first sentence, and each subsequent sentence adds a distinct warning, alternative, or side-effect without repetition. The structure is tight and appropriately sized.

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?

Given the output schema already covers return values and the schema documents all parameters, the description supplies the missing behavioral context: silent note handling, attendance-list behavior, and the correct tool for concluding a meeting. Nothing critical is left for the agent to infer.

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?

Schema coverage is 100%, so the baseline is 3, but the description adds meaning beyond the schema: notes are silently ignored, and participants changes do not affect attendance. It does not add further syntax or edge-case detail for topic or meeting_id, keeping it from a 5.

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 states a specific verb and resource: 'Update a meeting's topic or participant list.' It clearly distinguishes the tool from meeting_conclude and the task wall alternatives, so an agent can identify its exact scope without opening the schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It gives explicit routing: notes are not stored and conclusions belong on the task wall (task_create / task_update), and concluding a meeting requires meeting_conclude. The when-to-use and when-to-use-something-else guidance is direct and complete.

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

Deploy Server