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

TDQS

A3.6/5.0

Behavior4/5

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

Annotations already provide readOnlyHint, idempotentHint, and destructiveHint, so safety traits are covered. The description adds behavioral context beyond annotations: pagination behavior (limit/offset, response 'total' signals stop), sorting (soonest first), summary views, and a pointer to v1GetMeeting for full details. This is valuable context for an AI agent.

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 extremely concise and well-structured: a single front-loaded sentence for purpose and usage alternatives, followed by two additional sentences covering pagination and response detail level. Every sentence earns its place with no waste.

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?

Despite having an output schema (which explains return values), the description covers all necessary aspects: purpose, sibling differentiation, pagination, sort order, and what level of detail the returned items provide. It is complete for a read-only list tool with well-annotated safety profile.

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%, so the baseline is 3. The description mentions pagination with `limit` and `offset` and the meaning of `total`, which reinforces the schema's parameter descriptions but does not add new semantic detail beyond what is already in the schema. It adds no additional constraints or context for the agent.

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 provides explicit guidance on when to use this tool ('when the user asks what is coming up') and names two alternatives (listMeetings and searchMeetings) along with their distinct use cases. However, it does not cover when not to use it or any prerequisites.

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?