Skip to main content
Glama

Contio MeetingOS

by ai.contio

Find workspace contacts for meeting invitations or name-to-email resolution. Use this when the user gives only a name or initials and you need the matching email/address; pass any meeting id and an optional q. Use manageMeetingParticipants add to actually add them to a meeting. Searches workspace contacts for a meeting. Pass the meeting `id` and optional `q` (name/email substring). Use returned `email` as `guest_email` in v1AddMeetingParticipants. Does not expose registered-user status.

listMeetingContacts
Read-only

Find workspace contacts for meeting invitations or name-to-email resolution. Use this when the user gives only a name or initials and you need the matching email/address; pass any meeting id and an optional q. Use manageMeetingParticipants add to actually add them to a meeting.

Searches workspace contacts for a meeting. Pass the meeting id and optional q (name/email substring). Use returned email as guest_email in v1AddMeetingParticipants. Does not expose registered-user status.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
qNoSearch query matched against name or email
idYesMeeting ID
limitNoMaximum number of items per page (1-100, default 20)
offsetNoNumber of items to skip (default 0)

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
itemsNoArray of items for the current page
limitNoMaximum number of items per page
totalNoTotal number of items across all pages
offsetNoNumber 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 already declare readOnlyHint=true, so the description's mention of 'searching' is consistent. It adds value by stating that registered-user status is not exposed, a behavior not captured by annotations. No other behavioral gaps are noted, though the pagination behavior could be more explicit. However, with annotations covering safety, this is strong.

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 short paragraphs, starting with the core purpose. Every sentence adds new information: purpose, usage scenario, parameters, follow-up action, and a limitation. No filler or repetition, making it efficient for an agent to parse.

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?

The tool has 4 parameters (1 required), an output schema, and no nested objects. The description covers the search behavior, how to use results, and a key limitation. Pagination details are in the schema, and the output schema handles return values. The context is fully sufficient for correct invocation.

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% (all 4 parameters documented), but the description adds crucial context beyond the schema: it tells the agent to use the returned email as guest_email in another tool, and clarifies that q is a substring search. This goes beyond baseline schema documentation.

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?

The description provides explicit when-to-use guidance: 'when the user gives only a name or initials and you need the matching email/address'. It also names the alternative tool for the next step ('Use manageMeetingParticipants add to actually add them to a meeting') and notes a limitation ('Does not expose registered-user status'). This meets the highest criteria.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Contio MeetingOS toolsInspect
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