Contio MeetingOS

Browse meeting templates. Use this to see available templates; use the returned id with manageMeetings create to start a meeting from a template. Lists meeting templates usable by the caller (system, vertical, workspace, and personal). Call this to get a `template_id` for v1CreateMeeting. Paginate with `limit` (1–100, default 20) and `offset`. No paid-tier gating.

listMeetingTemplates

Read-onlyIdempotent

Browse meeting templates. Use this to see available templates; use the returned id with manageMeetings create to start a meeting from a template.

Lists meeting templates usable by the caller (system, vertical, workspace, and personal). Call this to get a template_id for v1CreateMeeting. Paginate with limit (1–100, default 20) and offset. No paid-tier gating.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`limit`	No	Maximum items per page (1-100)
`offset`	No	Number of items to skip

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.9/5.0

Behavior4/5

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

Annotations (readOnlyHint, idempotentHint, destructiveHint) already declare safe read behavior. Description adds valuable context: templates are scoped to caller (system, vertical, workspace, personal), pagination details, and 'No paid-tier gating'. This goes beyond annotations without contradicting them. One point off for not mentioning any rate limits or response structure beyond the output schema.

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?

Two compact sentences that front-load the primary purpose. Every sentence adds value: browsing, usage chaining, template scope, pagination, and free tier. No redundant 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?

Given the tool's simplicity (no required params, pagination, output schema present), the description is complete. It covers when to use, what templates are included, how to paginate, and tier availability. The output schema exists so return values need not be described.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema covers both parameters with descriptions (100% coverage). Description adds the default value for limit (20) and confirms pagination semantics. This is helpful beyond the schema, but offset is still minimally described. Baseline 3, plus 1 for adding default and range.

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 states when to use: 'Use this to see available templates' and 'Call this to get a template_id for v1CreateMeeting'. It also provides chaining guidance to manageMeetings. No alternative tool for listing templates exists among siblings, so exclusion is implicit but clear.

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?