Contio MeetingOS

View scheduled or discarded backlog items. Use this to see the backlog history; use listBacklogItems for active unscheduled items and getBacklogItem for one active item. Lists backlog items that have been assigned to a meeting or deleted (`assigned_at` or `deleted_at` set). These are terminal — they cannot be updated or reassigned. An id appears here or in v1ListBacklogItems, never both. Paginate with `limit` and `offset` (1–100).

listBacklogItemHistory

Read-onlyIdempotent

View scheduled or discarded backlog items. Use this to see the backlog history; use listBacklogItems for active unscheduled items and getBacklogItem for one active item.

Lists backlog items that have been assigned to a meeting or deleted (assigned_at or deleted_at set). These are terminal — they cannot be updated or reassigned. An id appears here or in v1ListBacklogItems, never both. Paginate with limit and offset (1–100).

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

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

Input 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 left the backlog

Output 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

Schema Changelog

Changes observed during successful MCP inspections.

First observedAug 11, 2026

TDQS

A3.6/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the tool is safe and idempotent. The description adds valuable behavioral context: items listed are 'terminal — they cannot be updated or reassigned', and an ID appears here or in v1ListBacklogItems, never both. This goes beyond what annotations provide, earning a 4.

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 concise with two paragraphs and front-loads the purpose in the first sentence. Every sentence adds value: sibling tool references, state explanation, and pagation constraints. It is not verbose, though it could be slightly shortened by removing redundant pagination detail that already exists in the schema.

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 output schema exists (so return values need not be described), annotations cover idempotency and safety, and schema covers all 3 parameters, the description completes the picture well. It explains the tool's scope (history of assigned/deleted items), terminal nature, and mutual exclusivity with listBacklogItems. Only minor missing context: it doesn't specify the default sort order behavior.

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 description coverage is 100%, so the schema already documents all three parameters. The description mentions pagination with `limit` and `offset` (1–100), which aligns with the schema descriptions. However, it does not add semantic meaning beyond what the schema provides for `sort_order`. A baseline of 3 is appropriate since 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?

The description provides explicit when-to-use guidance: 'Use this to see the backlog history; use listBacklogItems for active unscheduled items and getBacklogItem for one active item.' It also explains that items here are terminal and cannot be updated or reassigned, which preempts misuse. The pagination constraints (limit 1–100) are clearly stated.

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?