Contio MeetingOS

See the caller's soonest future meetings. Use this when the user asks what is coming up; use listMeetings to browse all meetings and searchMeetings to filter by criteria. Lists the caller's upcoming (future) meetings, soonest first. Paginate with `limit` and `offset`; the response `total` tells you when to stop. Items are summary views; use v1GetMeeting for full details.

listUpcomingMeetings

Read-onlyIdempotent

See the caller's soonest future meetings. Use this when the user asks what is coming up; use listMeetings to browse all meetings and searchMeetings to filter by criteria.

Lists the caller's upcoming (future) meetings, soonest first. Paginate with limit and offset; the response total tells you when to stop. Items are summary views; 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

A4/5.0

Behavior5/5

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

Annotations already declare readOnlyHint and idempotentHint, so the safety profile is covered. The description adds valuable behavioral details: it lists only future meetings, sorts soonest first, supports pagination with limit/offset, exposes a total field to signal stopping, and returns summary views rather than full details. This goes well beyond the structured annotations.

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?

The description is compact and front-loaded, with the core purpose and usage guidance in the first two sentences. There is mild redundancy between 'soonest future meetings' and 'Lists the caller's upcoming (future) meetings, soonest first,' so it is not perfectly tight, but it avoids unnecessary padding.

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?

For a simple read-only listing tool with a rich output schema, the description covers everything an agent needs: what is returned, ordering, pagination mechanics, when to stop, and where to go for full meeting details. It is complete without over-explaining.

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 for limit and offset is 100%, which establishes the baseline at 3. The description adds operational context beyond the schema by explaining that pagination uses limit/offset and that the response's total field indicates when to stop, which helps an agent paginate 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 Guidelines5/5

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

The description gives direct when-to-use guidance: 'Use this when the user asks what is coming up.' It also names the alternatives and their distinct purposes: listMeetings for browsing all meetings and searchMeetings for filtering by criteria, leaving no ambiguity about route selection.

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?