Contio MeetingOS

View the caller's active personal access tokens. Use this to see tokens; use deleteUserToken to revoke one. Lists the caller's own non-revoked personal access tokens. No special scope or role required. Returns a masked prefix plus scopes and timestamps; the full secret is never returned. Paginate with `limit`/`offset` (1–100). Token `id` is for v1DeleteUserToken — it is not the secret token string.

listUserTokens

Read-onlyIdempotent

View the caller's active personal access tokens. Use this to see tokens; use deleteUserToken to revoke one.

Lists the caller's own non-revoked personal access tokens. No special scope or role required. Returns a masked prefix plus scopes and timestamps; the full secret is never returned. Paginate with limit/offset (1–100). Token id is for v1DeleteUserToken — it is not the secret token string.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`limit`	No	Limit
`offset`	No	Offset

Output Schema

TableJSON Schema

Name	Required	Description	Default
`items`	No
`limit`	No
`total`	No
`offset`	No

TDQS

A4.2/5.0

Behavior5/5

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

Beyond annotations (readOnly, idempotent, non-destructive), description adds that only non-revoked tokens are returned, full secret never returned, and clarifies token id purpose. This provides valuable behavioral context.

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?

Mostly concise with front-loaded purpose. However, the title and description first sentence repeat nearly verbatim, causing minor redundancy. Still efficient overall.

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 output schema exists, description covers all behavioral aspects: pagination, security (masked prefix, no full secret), caller scope, and link to deletion tool. Complete for this tool's complexity.

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

Parameters5/5

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

Schema has only limit/offset with basic descriptions (100% coverage). Description adds meaning: pagination behavior, valid range 1-100, and clarifies that token id is for deletion, not the secret. Adds significant value beyond schema.

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?

Provides explicit guidance: 'Use this to see tokens; use deleteUserToken to revoke one.' Also notes no special scope/role required, making usage conditions 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?