Skip to main content
Glama
chrischall

iOffice MCP

by chrischall
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

io_list_reservations

Read-only

List iOffice reservations by date range, space ID, or user ID to find bookings. Supports search, sorting, and pagination for workplace scheduling.

Instructions

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

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
viewNoResponse 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.
limitNoMax results (default 50, max 100)
searchNoFilter by title or description
userIdNoFilter by organizer user ID
endDateNoFilter reservations ending on or before this date (ISO 8601)
orderByNoProperty to sort by (default: id)
spaceIdNoFilter by space/room ID
startAtNoPagination offset (default 0)
startDateNoFilter reservations starting on or after this date (ISO 8601)
orderByTypeNoSort direction (default: asc)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed12 schema fields changedv3.2.6
    • 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"
  2. First observedv3.2.1

TDQS

C2.9/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds only that filtering is supported, which is fully derivable from the schema; it says nothing about pagination defaults (limit 50/max 100), result ordering, or response shape behavior beyond what annotations and schema already carry.

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?

Two short sentences, front-loaded with the core action before the filter detail. Nothing is wasted, though the second sentence is largely redundant with the schema.

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 read tool with no output schema, the description is minimal but the schema is rich and self-documenting, so an agent can still call it correctly. It nonetheless omits pagination/limit behavior context and any routing guidance among the many sibling reservation tools.

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 10 parameters, including the verbose view-mode explanation. The description's summary of filterable dimensions (date range, space, user) maps directly onto startDate/endDate, spaceId, and userId and adds no meaning beyond the schema, so the baseline 3 applies.

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?

States a specific verb and resource ("List iOffice reservations") that clearly separates it from the singular io_get_reservation sibling. However, it never explicitly names that sibling or the io_create/update/delete_reservation tools, so differentiation is inferred from the naming convention rather than stated.

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

Usage Guidelines2/5

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

No guidance on when to use this tool versus io_get_reservation, io_list_spaces, or the other list endpoints. The mention of supported filters hints at usage but never states conditions, prerequisites, or alternatives.

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

Deploy Server

Other Tools