Skip to main content
Glama

Coline

Update meeting action item

update_meeting_action_item
Idempotent

Marks a meeting action item done or open, renames it, or gives it to someone.

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>",
      "eventId": "<eventId>",
      "itemId": "<itemId>"
    },
    "name": "update_meeting_action_item"
  }
}

Input Schema

NameRequiredDescriptionDefault
titleNo
itemIdYes
statusNo
eventIdYesEvent id from list_events.
workspaceYesWorkspace slug from workspaces.list, e.g. "acme".
assigneeUserIdNo

Output Schema

NameRequiredDescriptionDefault
okYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, idempotentHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is covered and the description only needs to add context. It does add the operation set, but omits partial-update semantics (are unspecified fields preserved?), what a null assigneeUserId does, and whether any permission is required to reassign someone else's item.

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?

One tight sentence in parallel verb form, with the resource stated first and the three mutations front-loaded. No filler, though the phrasing is brief enough that a little more structure (e.g. naming the field for each operation) would have cost nothing.

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?

An output schema and full annotations exist, so the description need not cover return values or safety. Still, for a six-parameter mutation with only a third of its schema documented, the definition should at minimum state that it is a partial update on an existing item — that gap remains.

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 only 33% (eventId and workspace), so the description must carry weight, and it does partially: it maps status to open/done, title to rename, and assigneeUserId to reassignment. It leaves itemId unexplained, does not state that a null assignee clears the owner, and does not clarify whether the three operations can be combined in one call.

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 description names a specific resource (meeting action item) and enumerates the three concrete mutations: set status open/done, rename via title, and reassign via assignee. That is enough to separate it from list_meeting_action_items and extract_meeting_action_items, but it never explicitly contrasts itself with those siblings or states that it only operates on already-existing items.

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 when-to-use or when-not-to-use guidance: nothing says this requires an item created or extracted earlier, nothing rules out using it on completed items, and no alternative is named. The only routing help (eventId from list_events, workspace from workspaces.list) lives in the schema, not the description.

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