iOffice MCP

io_list_reservations

Read-only

List iOffice reservations and filter by date range, space, user, or search term to locate relevant bookings and availability.

Instructions

List iOffice reservations. Supports filtering by date range, space, or user.

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": "io_list_reservations"
  }
}

Input Schema

Name	Required	Description
`view`	No	Response shape. compact strips image/avatar URLs from the response; "full" returns iOffice's payload untouched. No field projection: this server has no verified record of which iOffice fields matter, and inventing one would risk dropping a field a caller needs. "brief" returns one line per item — title — <ISO date or "no date"> — <status> — with "-- " note lines for an empty or partial page.
`limit`	No	Max results (default 50, max 100)
`search`	No	Filter by title or description
`userId`	No	Filter by organizer user ID
`endDate`	No	Filter reservations ending on or before this date (ISO 8601)
`orderBy`	No	Property to sort by (default: id)
`spaceId`	No	Filter by space/room ID
`startAt`	No	Pagination offset (default 0)
`startDate`	No	Filter reservations starting on or after this date (ISO 8601)
`orderByType`	No	Sort direction (default: asc)

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedv3.3.0Nov 5, 2026

changedInput schema / properties / view / description

Previous value: -"Response shape: \"compact\" (default) drops fields the response already carries elsewhere; \"full\" returns every field this server understands. compact strips image/avatar URLs from the response; \"full\" returns iOffice's payload untouched. No field projection: this server has no verified record of which iOffice fields matter, and inventing one would risk dropping a field a caller needs."New value: +"Response shape. compact strips image/avatar URLs from the response; \"full\" returns iOffice's payload untouched. No field projection: this server has no verified record of which iOffice fields matter, and inventing one would risk dropping a field a caller needs. \"brief\" returns one line per item — title — <ISO date or \"no date\"> — <status> — with \"-- \" note lines for an empty or partial page."

changedInput schema / properties / view / enum

Previous value: -[
-  "compact",
-  "full"
-]New value: +[
+  "compact",
+  "full",
+  "brief"
+]

Changed12 schema fields changedv3.2.6Oct 17, 2026
- addedInput schema / properties / limit / maximum
```
Added value: +100
```
- addedInput schema / properties / limit / minimum
```
Added value: +1
```
- changedInput schema / properties / limit / type
```
Previous value: -"number"New value: +"integer"
```
- addedInput schema / properties / spaceId / exclusiveMinimum
```
Added value: +0
```
- addedInput schema / properties / spaceId / maximum
```
Added value: +9007199254740991
```
- changedInput schema / properties / spaceId / type
```
Previous value: -"number"New value: +"integer"
```
- addedInput schema / properties / startAt / maximum
```
Added value: +9007199254740991
```
- addedInput schema / properties / startAt / minimum
```
Added value: +0
```
- changedInput schema / properties / startAt / type
```
Previous value: -"number"New value: +"integer"
```
- addedInput schema / properties / userId / exclusiveMinimum
```
Added value: +0
```
- addedInput schema / properties / userId / maximum
```
Added value: +9007199254740991
```
- changedInput schema / properties / userId / type
```
Previous value: -"number"New value: +"integer"
```
First observedv3.2.1Sep 27, 2026

TDQS

B3.3/5.0

Behavior2/5

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

Annotations already declare readOnlyHint and openWorldHint, so the safety profile is covered elsewhere. The description adds almost nothing beyond that: it does not mention pagination (limit/startAt), the default sort or the view/shape options, all of which materially change the call. It also advertises only three filter axes while the schema offers more, making the summary of behavior slightly incomplete.

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 short sentences with zero filler, and the core purpose is front-loaded ahead of the filter summary. Nothing needs trimming.

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

Completeness3/5

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

For a 10-parameter tool with no output schema, the description does the minimum. The view parameter's schema text covers response shape and pagination is documented per-parameter, but the description itself says nothing about result paging, default ordering, or what a caller gets back.

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 parameters are already fully documented in structured data; baseline 3 applies. The description's mention of date range, space, and user filtering restates existing schema content and adds no format, syntax, or interaction detail (e.g., how startDate interacts with endDate).

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

"List iOffice reservations" states a specific verb and resource, and the second sentence names the supported filter axes. It is clear what the tool does, though it never references the sibling io_get_reservation to explain why one would list rather than fetch a single record.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

"Supports filtering by date range, space, or user" implies the situations where the tool is appropriate, but there is no explicit when-to-use guidance, no prerequisites, and no statement of when not to use it or which sibling to prefer.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server