Contio MeetingOS

Read the details of a single agenda item. Use this when the user asks about one agenda item; use listAgendaItems to see the full agenda. Fetches a single agenda item by `{id}`. Items outside the caller's workspace and backlog (meeting-less) items are hidden as 404. Use this to read `status`, `title`, and `time_allocation_minutes` without re-listing.

getAgendaItem

Read-onlyIdempotent

Read the details of a single agenda item. Use this when the user asks about one agenda item; use listAgendaItems to see the full agenda.

Fetches a single agenda item by {id}. Items outside the caller's workspace and backlog (meeting-less) items are hidden as 404. Use this to read status, title, and time_allocation_minutes without re-listing.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`id`	Yes	Agenda item ID

Output Schema

TableJSON Schema

Name	Required	Description
`id`	No
`title`	No
`status`	No
`deferred`	No
`sequence`	No
`item_type`	No
`created_at`	No
`meeting_id`	No
`presenters`	No	Presenters for this agenda item, enriched with name and email when the user record is available and belongs to the caller's workspace. Presenters outside it carry only user_id.
`updated_at`	No
`description`	No	Detailed description of the agenda item, in Markdown. Empty when the item has no description.
`talking_points`	No	Private talking points for the authenticated user on this agenda item, in Markdown. Only returned when the user has talking points.
`time_allocation_minutes`	No

TDQS

A3.8/5.0

Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint. Description adds value by disclosing that items outside the caller's workspace and backlog items are hidden as 404, and by naming specific returned fields (status, title, time_allocation_minutes). 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.

Conciseness5/5

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

Two concise sentences, front-loaded with purpose, no redundant words. Every sentence contributes meaning: purpose, sibling guidance, behavioral detail, and parameter usage.

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?

Tool is simple (1 param, annotated, has output schema). Description covers purpose, when to use, special behaviors, and which fields are readable. Output schema already handles return value documentation, so no additional explanation needed.

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% (single id parameter described in schema). The description mentions fetching by `{id}` but does not add semantic detail beyond the schema (e.g., format, constraints, or examples). Baseline 3 applies as schema already fully describes the parameter.

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 when-to-use guidance ('when user asks about one agenda item') and when-not-to ('use listAgendaItems for full agenda'), plus special behavioral context (items outside workspace or backlog return 404).

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?