Contio MeetingOS

Read the details of one follow-up task. Use this when the user asks about a specific action item; use listActionItems to see all tasks. Fetches a single action item by `{id}`. The item is only returned if the caller is the assignee or a participant in the parent meeting, so inaccessible ids return 404. Use this to read `status`, `is_completed`, and `due_date` without re-listing.

getActionItem

Read-onlyIdempotent

Read the details of one follow-up task. Use this when the user asks about a specific action item; use listActionItems to see all tasks.

Fetches a single action item by {id}. The item is only returned if the caller is the assignee or a participant in the parent meeting, so inaccessible ids return 404. Use this to read status, is_completed, and due_date without re-listing.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`id`	Yes	Action Item ID

Output Schema

TableJSON Schema

Name	Required	Description
`id`	No
`title`	No
`status`	No
`due_date`	No
`created_at`	No
`meeting_id`	No
`updated_at`	No
`description`	No	Longer description of the action item, in Markdown. Empty when the item has no description.
`completed_at`	No
`is_completed`	No
`agenda_item_id`	No
`assigned_to_name`	No	Display name of an external assignee; set only when assigned_to_user_id is omitted
`assigned_to_email`	No	Email of an external assignee (status delegated); set only when assigned_to_user_id is omitted
`assigned_to_user_id`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedOct 20, 2026

addedOutput schema / properties / assigned_to_email

Added value: +{
+  "description": "Email of an external assignee (status delegated); set only when assigned_to_user_id is omitted",
+  "type": "string"
+}

addedOutput schema / properties / assigned_to_name

Added value: +{
+  "description": "Display name of an external assignee; set only when assigned_to_user_id is omitted",
+  "type": "string"
+}

First observedAug 11, 2026

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/non-destructive, so the safety profile is covered. The description adds genuinely useful behavior beyond that: an authorization rule (only assignee or parent-meeting participant) and the resulting 404 for inaccessible ids, plus a note that it avoids re-listing.

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 tight sentences, front-loaded with the purpose and the sibling routing, followed by the access constraint. No filler; every clause earns its place.

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?

Output schema exists so return values need not be spelled out, and the description still highlights the key fields (status, is_completed, due_date). For a single-id read tool, the agent has everything needed to call it and interpret failures.

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?

Single required 'id' parameter at 100% schema description coverage, so the schema already documents it; the description only refers to it as '{id}' without adding format or lookup guidance. Baseline 3 applies when the schema does the heavy lifting.

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?

States the exact trigger ('when the user asks about a specific action item') and names the alternative tool plus the condition that selects it ('use listActionItems to see all tasks'). Nothing left to inference.

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

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?