Contio MeetingOS

Browse meeting templates. Use this to see available templates; use the returned id with manageMeetings create or update to seed a meeting from a template. Lists meeting templates usable by the caller (system, vertical, workspace, and personal). A template bundles agenda items, participants, facilitator prompts, and notes; applying one materializes that content onto a meeting additively (existing content is preserved). Call this to get a `template_id`, then pass it to v1CreateMeeting (applied asynchronously after creation — confirm via `applied_template_ids` on v1GetMeeting) or v1UpdateMeeting (applied synchronously). 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 or update to seed a meeting from a template.

Lists meeting templates usable by the caller (system, vertical, workspace, and personal). A template bundles agenda items, participants, facilitator prompts, and notes; applying one materializes that content onto a meeting additively (existing content is preserved). Call this to get a template_id, then pass it to v1CreateMeeting (applied asynchronously after creation — confirm via applied_template_ids on v1GetMeeting) or v1UpdateMeeting (applied synchronously). 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

Schema Changelog

Changes observed during successful MCP inspections.

First observedAug 11, 2026

TDQS

A4/5.0

Behavior5/5

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

Annotations already mark it readOnly/idempotent/non-destructive; the description adds behavioral detail beyond that: caller-visible template scopes, additive application semantics, async-vs-sync timing, pagination defaults, and absence of paid-tier gating. 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.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The text is denser than necessary (e.g., 'Browse meeting templates' and 'Use this to see available templates' overlap), but it front-loads the primary purpose and every additional sentence contributes operational value. Well-structured into purpose and follow-up details.

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?

For a simple paginated list with an output schema, the description covers all operational context: scope, pagination, downstream usage, application timing, and gating. Nothing an agent needs to call it correctly is missing.

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 coverage is 100% and only two parameters exist, so baseline is 3. The description adds the default limit of 20 and frames limit/offset as pagination, which is meaningful behavior not present in the schema descriptions.

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 says 'Use this to see available templates' and instructs passing the returned id to v1CreateMeeting or v1UpdateMeeting. It even clarifies async vs synchronous application, so an agent knows when this tool is the right first step.

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

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?