Contio MeetingOS

Read the full details of a meeting. Use this when the user asks about a specific meeting by id; use listMeetings or searchMeetings to find one and listUpcomingMeetings for the next scheduled ones. Fetches a meeting by `{id}`. `summary_notes` is present when a summary exists; PRO+ callers get full text, FREE-tier callers get a truncated preview. `applied_template_ids` lists the templates applied to the meeting — updated synchronously by PATCH and asynchronously after a templated create, so poll it to confirm a create-time `template_id` finished applying. A non-null `redirect_to_meeting_id` means the meeting was merged into another. Unknown or inaccessible ids return 404.

getMeeting

Read-onlyIdempotent

Read the full details of a meeting. Use this when the user asks about a specific meeting by id; use listMeetings or searchMeetings to find one and listUpcomingMeetings for the next scheduled ones.

Fetches a meeting by {id}. summary_notes is present when a summary exists; PRO+ callers get full text, FREE-tier callers get a truncated preview. applied_template_ids lists the templates applied to the meeting — updated synchronously by PATCH and asynchronously after a templated create, so poll it to confirm a create-time template_id finished applying. A non-null redirect_to_meeting_id means the meeting was merged into another. Unknown or inaccessible ids return 404.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`id`	Yes	Meeting ID

Output Schema

TableJSON Schema

Name	Required	Description
`id`	No	Unique identifier for the meeting
`title`	No	Title of the meeting
`status`	No	Current status of the meeting
`end_time`	No	Scheduled end time in RFC3339 format
`created_at`	No	Timestamp when the meeting was created
`start_time`	No	Scheduled start time in RFC3339 format
`updated_at`	No	Timestamp when the meeting was last updated
`template_id`	No	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
`workspace_id`	No	ID of the workspace this meeting belongs to
`match_context`	No	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).
`summary_notes`	No	AI-generated summary notes from the meeting. Only populated on the single-meeting GET; PRO+ callers receive the full summary while FREE-tier callers receive a truncated preview (first 200 characters) followed by an upgrade note. Omitted in list/search/upcoming views.
`owned_by_user_id`	No	ID of the user who owns the meeting
`calendar_event_id`	No	ID of the linked calendar event, if any
`created_by_user_id`	No	ID of the user who created the meeting
`applied_template_ids`	No	IDs of the meeting templates applied to this meeting; updated synchronously by PATCH and asynchronously after a templated create
`redirect_to_meeting_id`	No	ID of the meeting to redirect to if this meeting was merged

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedSep 22, 2026

changedOutput schema / 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 / 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 / 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 / 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 cover read-only and idempotent, but the description adds substantial behavioral detail: summary_notes content varies by tier, applied_template_ids update asynchronously and require polling, redirect_to_meeting_id signals merges, and 404 for unknown/inaccessible ids. These go far beyond the basic annotation hints and help the agent handle edge cases correctly.

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 structured into two clear paragraphs: the first states purpose and when to use, the second covers behavioral nuances. It is concise, front-loaded, and every sentence adds value—no fluff or repetition.

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 single-parameter read tool, this is thorough. It covers important return fields (summary_notes, applied_template_ids, redirect_to_meeting_id), tier differences, polling guidance, and error behavior (404). The presence of an output schema further reduces the need to describe returns, but the description still provides valuable context an agent needs to correctly interpret results.

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?

The schema already describes the single `id` parameter with 100% coverage, so the description doesn't need to explain it. The description references `{id}` but adds no additional semantic meaning about the parameter's format, constraints, or usage beyond what the schema provides. Baseline 3 is appropriate.

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?

It explicitly says 'Use this when the user asks about a specific meeting by id' and lists the alternatives and their conditions. It also provides guidance on when not to use it (e.g., to list meetings, use listMeetings or searchMeetings). This gives clear, actionable usage context.

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?