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. 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. 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
`workspace_id`	No	ID of the workspace this meeting belongs to
`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
`redirect_to_meeting_id`	No	ID of the meeting to redirect to if this meeting was merged

TDQS

A4/5.0

Behavior5/5

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

Beyond annotations (readOnlyHint, idempotentHint, destructiveHint), the description adds critical behavioral details: summary_notes presence and tier-dependent truncation, redirect_to_meeting_id meaning, and 404 response. No contradiction with annotations.

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 concise (four sentences), front-loaded with purpose and usage guidance, and contains no redundant or extraneous information. Every sentence adds value.

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?

Given the tool's simplicity (single parameter, output schema present, rich annotations), the description covers purpose, usage, error handling, and special behaviors (summary, redirect). It is fully adequate for an agent to select and invoke the tool 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?

The input schema covers the single parameter 'id' with 'Meeting ID' (100% coverage). The description does not add new semantic meaning to the parameter beyond stating it fetches by that id, but it does explain error behavior for invalid IDs. 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?

The description provides explicit when-to-use guidance ('when the user asks about a specific meeting by id') and names alternative tools for different scenarios. It also mentions that unknown or inaccessible ids return 404, aiding error handling.

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

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A3.8/5.0

Disambiguation4/5

Tools are mostly distinct, with clear separation between meetings, agenda/backlog items, action items, participants, and calendar events. However, `manageMeetingContent` bundles both raw file attachments and AI context documents into one tool, which could cause confusion for an agent deciding which contentType variant to use.

Naming Consistency4/5

The naming follows a consistent verb_noun pattern (e.g., `listMeetings`, `getMeeting`, `deleteUserToken`), but there are minor deviations like `manageMeetingItems` (verb_noun) vs `manageActionItems` (verb_noun) and `getMeetingTranscript` which is consistent, but `getMe` breaks the pattern as a short form. Overall, predictable and well-organized.

Tool Count4/5

With 30 tools, the count is on the higher side but reasonable given the broad domain covering meetings, agenda, backlogs, action items, participants, calendar events, user tokens, and content management. Each tool serves a specific purpose, though a slight reduction by combining some closely related functions could improve focus.

Completeness4/5

The tool surface covers the core lifecycle for meetings, agenda/backlog items, action items, participants, and content management. Minor gaps exist, such as the lack of tools for managing meeting templates (only listed, not created/deleted) and no tool for sending invitations via email, but these are not critical for the main use cases.

Resources

Need Help?