Contio MeetingOS

View calendar events in a time range. Use this to see multiple events; use getCalendarEvent for the details of a single event. Lists the caller's calendar events between `start_date` and `end_date` (both required ISO-8601). Paginate with `limit` and `offset` (1–100) and control ordering with `direction`. An empty result usually means no events in the range.

listCalendarEvents

Read-onlyIdempotent

View calendar events in a time range. Use this to see multiple events; use getCalendarEvent for the details of a single event.

Lists the caller's calendar events between start_date and end_date (both required ISO-8601). Paginate with limit and offset (1–100) and control ordering with direction. An empty result usually means no events in the range.

Input Schema

TableJSON Schema

Name	Required	Description
`limit`	No	Number of results per page (default 25, max 100)
`offset`	No	Pagination offset (default 0)
`end_date`	Yes	End time in RFC3339 format
`direction`	No	Sort direction: asc or desc (default: asc)
`start_date`	Yes	Start time in RFC3339 format

Output Schema

TableJSON Schema

Name	Required	Description
`items`	No	Array of calendar events 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

TDQS

A3.5/5.0

Behavior4/5

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

Annotations already provide readOnlyHint, idempotentHint, and destructiveHint. The description adds valuable context: that events belong to the caller, required date range format (ISO-8601), pagination limits (1–100), and interpretation of empty results. No contradictions 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, using only 5 sentences. It is front-loaded with the purpose and sibling distinction, then provides essential operational details. Every sentence adds value without redundancy.

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 tool's complexity (5 parameters, 2 required, output schema present), the description covers purpose, when to use, parameter roles, pagination, ordering, and result interpretation. It could mention authentication scoping (assumed from 'caller'), but overall it is complete for an AI agent to use 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?

Schema coverage is 100% with detailed descriptions for all 5 parameters. The description reiterates the required parameters and format, and adds a pagination range (1–100) that partially overlaps the schema's 'max 100' and default. The added value beyond the schema is modest, so a 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 Guidelines4/5

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

The description explicitly tells when to use this tool ('to see multiple events') and when to use the sibling 'getCalendarEvent' ('for the details of a single event'). It also explains that an empty result usually means no events. However, it could be stronger by explicitly stating not to use this for modifications (given the presence of 'manageCalendarEvents' in siblings).

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?