Contio MeetingOS

List AI context documents on a meeting. Use this to see background docs; use getMeetingContext for one doc's metadata and manageMeetingContent download for the actual text; raw files are listed with listMeetingAttachments. Lists context documents on a meeting. Use as the discovery call before v1GetMeetingContext or v1DownloadMeetingContextContent. Text-biased AI-visible documents only; list raw files with v1ListMeetingAttachments. Paginate with `limit`/`offset` (clamped 1–100). 404 unknown/out-of-workspace meeting.

listMeetingContext

Read-onlyIdempotent

List AI context documents on a meeting. Use this to see background docs; use getMeetingContext for one doc's metadata and manageMeetingContent download for the actual text; raw files are listed with listMeetingAttachments.

Lists context documents on a meeting. Use as the discovery call before v1GetMeetingContext or v1DownloadMeetingContextContent. Text-biased AI-visible documents only; list raw files with v1ListMeetingAttachments. Paginate with limit/offset (clamped 1–100). 404 unknown/out-of-workspace meeting.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "id": "<id>"
    },
    "name": "listMeetingContext"
  }
}

Input Schema

Name	Required	Description
`id`	Yes	Meeting ID
`limit`	No	Maximum number of items to return (1-100)
`offset`	No	Offset for pagination

Output Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

First observedAug 11, 2026

TDQS

A3.7/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the description doesn't contradict them. It adds behavioral context beyond annotations: pagination bounds (1–100), the 404 error for unknown/out-of-workspace meetings, and that it returns only text-biased AI-visible documents. Minor deduction: no mention of response structure or whether the list is ordered, though output schema exists.

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 front-loaded with the core action, uses a second paragraph for supplemental details (alternatives, pagination, errors). Slight redundancy between paragraphs (both mention alternatives and raw file listing). Could be tightened by removing one sentence without losing meaning. Still efficient overall.

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?

With 3 parameters, 100% schema coverage, a read-only annotation, and an output schema, the description is nearly complete. It covers purpose, alternatives, pagination, and errors. Minor gap: doesn't clarify that the output is likely a list summary (metadata, not content), but the output schema exists and the tool name implies context metadata. For a discovery tool, it's sufficient.

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

Parameters4/5

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

Schema description coverage is 100%, so the schema already documents id, limit, and offset with types and descriptions. The description adds value by stating that limit/offset are 'clamped 1–100' and that 404 occurs for invalid meetings, which goes beyond schema. Baseline 3, plus 1 for additional context.

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?

It explicitly tells when to use this tool (as discovery before getMeetingContext or download), when not to (for raw files, use listMeetingAttachments), and provides pagination details with limit/offset clamping. The alternatives are named: getMeetingContext and manageMeetingContent download.

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?