Contio MeetingOS

Read the details of one calendar event. Use this when the user asks about a specific event; use listCalendarEvents to see events in a time range. Fetches a single calendar event for the authenticated user, keyed by the `{id}` from v1ListCalendarEvents; requires the `meetings:read` scope. Use it to read the full detail of an event you already discovered via the list call. Returns 404 if the id is unknown or the event does not belong to the caller.

getCalendarEvent

Read-onlyIdempotent

Read the details of one calendar event. Use this when the user asks about a specific event; use listCalendarEvents to see events in a time range.

Fetches a single calendar event for the authenticated user, keyed by the {id} from v1ListCalendarEvents; requires the meetings:read scope. Use it to read the full detail of an event you already discovered via the list call. Returns 404 if the id is unknown or the event does not belong to the caller.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`id`	Yes	Calendar Event ID

Output Schema

TableJSON Schema

Name	Required	Description
`id`	No	Unique identifier for the calendar event
`title`	No	Title of the calendar event
`end_time`	No	End time of the event in RFC3339 format
`location`	No	Location of the event (physical or virtual)
`attendees`	No	List of attendees for the calendar event
`organizer`	No	Organizer of the calendar event
`start_time`	No	Start time of the event in RFC3339 format
`description`	No	Description or body of the calendar event
`linked_meetings`	No	IDs of all linked Contio meetings, sorted by creation date (oldest first)

TDQS

A3.5/5.0

Behavior3/5

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

Annotations already provide readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the description doesn't need to cover safety. It adds value by stating the required scope ('meetings:read') and that it returns 404 for unknown or non-owned events, which is useful but not extensive behavioral context.

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 two tightly written sentences, front-loaded with the core purpose and usage guidance, followed by a sentence adding technical detail (scoping, error behavior). No wasted words.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the high schema coverage (100%), clear annotations, and a single required parameter, the description is nearly complete. It covers purpose, usage, prerequisites (id from list call), auth scope, and error condition. Could potentially add how to retrieve the id if not already discovered, but that is tangential. The output schema exists, so return value details are not needed in the description.

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 has 100% coverage with a single parameter 'id' described as 'Calendar Event ID'. The description adds that the id comes from v1ListCalendarEvents, which is helpful context, but since the schema already describes the parameter, the baseline is 3.

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?

Explicitly tells when to use this tool ('when the user asks about a specific event') and when to use an alternative ('use listCalendarEvents to see events in a time range'). Also clarifies it depends on first discovering the event via the list call, providing clear 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

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?