Contio MeetingOS

See unscheduled agenda items in the backlog. Use this to view active backlog items; use getBacklogItem for one item's details and listBacklogItemHistory for used or discarded ones. Lists the caller's active (unscheduled) backlog items. Items assigned or deleted are excluded — use v1ListBacklogItemHistory for those. Paginate with `limit` and `offset` (1–100). Each item's `id` is the backlog handle, not `agenda_item_id`.

listBacklogItems

Read-onlyIdempotent

See unscheduled agenda items in the backlog. Use this to view active backlog items; use getBacklogItem for one item's details and listBacklogItemHistory for used or discarded ones.

Lists the caller's active (unscheduled) backlog items. Items assigned or deleted are excluded — use v1ListBacklogItemHistory for those. Paginate with limit and offset (1–100). Each item's id is the backlog handle, not agenda_item_id.

Input Schema

TableJSON Schema

Name	Required	Description
`limit`	No	Maximum items per page (1-100)
`offset`	No	Number of items to skip
`sort_order`	No	Sort direction on the time the item reached the backlog

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

Behavior5/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, so the tool is safe. The description adds valuable context: it lists only the caller's items, excludes assigned/deleted, paginates with limit/offset (1-100), and notes that 'id' is the backlog handle, not agenda_item_id. No contradictions.

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 concise paragraphs: the first front-loads the purpose and sibling alternatives, the second adds details on scope, exclusions, pagination, and id field. Every sentence adds value, no redundancy.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the schema fully describes all parameters, annotations are present, and an output schema exists, the description covers usage, exclusions, pagination, and id semantics. Minor gap: sort_order options are not detailed beyond what the schema says, but overall it is sufficiently complete.

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?

Schema coverage is 100%, so baseline is 3. The description mentions pagination with limit/offset (1-100) and the id field nuance, but does not add meaning for sort_order beyond what the schema already provides ('Sort direction on the time the item reached the backlog'). Minimal extra value.

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?

Explicit when-to-use guidance is provided: 'Use this to view active backlog items; use getBacklogItem for one item's details and listBacklogItemHistory for used or discarded ones.' It also clarifies what is excluded ('Items assigned or deleted are excluded') and names the alternative tool for those.

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?