Contio MeetingOS

Read the current user's identity and workspace context. Use this when the user asks about who they are, their plan, or their workspace. Returns the authenticated user's public identity and the workspace context carried by the current credential. Use this to resolve the caller's user id, email, workspace id, workspace role, and plan before invoking operations that require those identifiers. The endpoint requires authentication but no resource scope, and repeated calls do not change state.

getMe

Read-onlyIdempotent

Read the current user's identity and workspace context. Use this when the user asks about who they are, their plan, or their workspace.

Returns the authenticated user's public identity and the workspace context carried by the current credential. Use this to resolve the caller's user id, email, workspace id, workspace role, and plan before invoking operations that require those identifiers. The endpoint requires authentication but no resource scope, and repeated calls do not change state.

Input Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Output Schema

TableJSON Schema

Name	Required	Description	Default
`id`	No
`email`	No
`timezone`	No
`plan_type`	No
`created_at`	No
`display_name`	No
`workspace_id`	No
`workspace_name`	No
`workspace_role`	No

TDQS

A3.5/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is well-covered. The description adds that authentication is required but no resource scope, and that repeated calls do not change state. This aligns with annotations but doesn't reveal additional behavioral nuance beyond what annotations already indicate.

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 description is concise and front-loaded with the purpose and usage. The only redundancy is that the title and description repeat the same information. The text could be slightly shortened without losing meaning, but it remains efficient.

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 that the tool has zero parameters, rich annotations, and an output schema that presumably details the return structure, the description completely covers the necessary context. It explains the purpose, when to use it, and the authentication model. There is no gap.

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?

The input schema has zero parameters and schema description coverage is 100%, so there is nothing to add. The description does mention what the tool returns (user id, email, workspace id, etc.), which adds some value but is not about parameters. Baseline 3 is appropriate since the schema requires no compensation.

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 explicitly states when to use it ('when the user asks about who they are, their plan, or their workspace') and suggests using it before operations that require identifiers like user id or workspace id. It does not specify when not to use it, but the explicit usage context is sufficient.

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?