Contio MeetingOS

Browse or paginate the caller's meetings. Use this to see all meetings; prefer searchMeetings when the user mentions keyword, date, participant, or status, and listUpcomingMeetings for the soonest future ones. Lists the caller's workspace meetings, newest first. Paginate with `limit` and `offset`; the response `total` tells you when to stop. Items are summary views and never include `summary_notes`; use v1GetMeeting for full details.

listMeetings

Read-onlyIdempotent

Browse or paginate the caller's meetings. Use this to see all meetings; prefer searchMeetings when the user mentions keyword, date, participant, or status, and listUpcomingMeetings for the soonest future ones.

Lists the caller's workspace meetings, newest first. Paginate with limit and offset; the response total tells you when to stop. Items are summary views and never include summary_notes; use v1GetMeeting for full details.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`limit`	No	Maximum items per page (1-100, default 20)
`offset`	No	Number of items to skip (default 0)

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.

Changed2 schema fields changedSep 22, 2026

changedOutput schema / properties / items / items / properties / applied_template_ids / description

Previous value: -"AppliedTemplateIDs is the list of template IDs that have been applied to this meeting"New value: +"IDs of the meeting templates applied to this meeting; updated synchronously by PATCH and asynchronously after a templated create"

addedOutput schema / properties / items / items / properties / template_id

Added value: +{
+  "description": "ID of the meeting template linked via template_id on create or update, if any. Linking alone does not mean the template content has been applied — see applied_template_ids",
+  "type": "string"
+}

Changed1 schema field changedSep 15, 2026

addedOutput schema / properties / items / items / properties / match_context

Added value: +{
+  "description": "A highlighted snippet from the meeting's notes explaining why a `q` search matched. Only populated by search endpoints when a query is provided and the match came from notes content; omitted otherwise (e.g. title-only matches).",
+  "type": "string"
+}

Changed1 schema field changedSep 8, 2026

addedOutput schema / properties / items / items / properties / applied_template_ids

Added value: +{
+  "description": "AppliedTemplateIDs is the list of template IDs that have been applied to this meeting",
+  "items": {
+    "type": "string"
+  },
+  "type": "array"
+}

First observedAug 11, 2026

TDQS

A3.9/5.0

Behavior5/5

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

Annotations already mark this as read-only, idempotent, and non-destructive. The description adds meaningful behavioral context beyond that: newest-first ordering, limit/offset pagination, the total field as the stop signal, and the fact that items are summary views that never include summary_notes.

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 description is tightly structured: it opens with scope, immediately routes to alternatives, then covers ordering, pagination, and payload limitations. Every sentence adds information and there is no filler or repetition of schema content.

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?

With an output schema present and annotations covering the safety profile, the description only needs to convey selection logic and behavioral details. It does so completely: when to use this tool, how pagination works, what summary views exclude, and which alternative provides full details.

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?

The input schema fully documents limit and offset with defaults and ranges, so the baseline is 3. The description adds useful pagination semantics by saying how the two parameters work together and that the response total tells you when to stop paginating, which helps an agent use the parameters correctly.

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?

The description gives clear when-to-use guidance: use this to see all meetings, prefer searchMeetings for keyword/date/participant/status, prefer listUpcomingMeetings for soonest future ones, and use v1GetMeeting for full details. The only small gap is that v1GetMeeting is not an exact match to the sibling tool name getMeeting, which may cause slight resolution ambiguity.

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?