Contio MeetingOS

View follow-up tasks across meetings. Use this to see action items assigned to the caller; use getActionItem for the details of a single task. Lists action items assigned to the caller. Filter by `meeting_id` and/or `status`; paginate with `limit` and `offset` (1–100). Items assigned to other members are not returned. Use this to discover ids for v1UpdateActionItem and v1DeleteActionItem.

listActionItems

Read-onlyIdempotent

View follow-up tasks across meetings. Use this to see action items assigned to the caller; use getActionItem for the details of a single task.

Lists action items assigned to the caller. Filter by meeting_id and/or status; paginate with limit and offset (1–100). Items assigned to other members are not returned. Use this to discover ids for v1UpdateActionItem and v1DeleteActionItem.

Input Schema

TableJSON Schema

Name	Required	Description
`limit`	No	Maximum items per page (1-100)
`offset`	No	Number of items to skip
`status`	No	Filter by status. delegated lists items assigned to someone outside the workspace
`meeting_id`	No	Filter by meeting ID

Output Schema

TableJSON Schema

Name	Required	Description
`items`	No	Array of items for the current page
`limit`	No	Maximum number of items per page
`total`	No	Total number of items across all pages
`offset`	No	Number of items skipped from the beginning

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedOct 20, 2026

changedInput schema / properties / status / description

Previous value: -"Filter by status"New value: +"Filter by status. delegated lists items assigned to someone outside the workspace"

addedOutput schema / properties / items / items / properties / assigned_to_email

Added value: +{
+  "description": "Email of an external assignee (status delegated); set only when assigned_to_user_id is omitted",
+  "type": "string"
+}

addedOutput schema / properties / items / items / properties / assigned_to_name

Added value: +{
+  "description": "Display name of an external assignee; set only when assigned_to_user_id is omitted",
+  "type": "string"
+}

First observedAug 11, 2026

TDQS

A3.5/5.0

Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, so safety is covered. The description adds genuinely useful behavioral scope beyond that: items assigned to other members are never returned, and it documents the pagination range (1-100). It stops short of describing ordering or total-count behavior.

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?

Front-loaded with the core purpose and alternatives in the first sentence. There is some duplication between the title sentence and the body (both restate "action items assigned to the caller"), costing a point but not hurting comprehension.

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?

An output schema exists, so return values need not be explained, and annotations carry the safety profile. Combined with full schema coverage and stated filtering/pagination behavior, an agent has everything needed to invoke this correctly.

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 description coverage is 100%, so all four parameters are already documented in the schema. The description restates the limit range and filter combinations but adds no new format or semantics beyond what the schema provides, which is the correct baseline-3 case.

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

Purpose2/5

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

Tautological: description restates name/title.

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?

Gives clear selection guidance (use this for lists, getActionItem for a single task) and states the purpose of discovery for downstream update/delete calls. However, the named downstream tools (v1UpdateActionItem, v1DeleteActionItem) do not match any name in the sibling tool list, which weakens the routing slightly.

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

All Contio MeetingOS 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?