iOffice MCP

io_list_floors

Read-only

List iOffice floors, optionally filtered by building ID, to view or choose facility levels.

Instructions

List iOffice floors. Optionally filter by building ID.

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_floors"
  }
}

Input Schema

Name	Required	Description
`view`	No	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.
`limit`	No	Max results (default 50, max 100)
`search`	No	Filter by name
`orderBy`	No	Property to sort by (default: id)
`startAt`	No	Pagination offset (default 0)
`buildingId`	No	Filter floors by building ID
`orderByType`	No	Sort direction (default: asc)

Schema Changelog

Changes observed during successful MCP inspections.

Changed9 schema fields changedv3.2.6Oct 17, 2026
- addedInput schema / properties / buildingId / exclusiveMinimum
```
Added value: +0
```
- addedInput schema / properties / buildingId / maximum
```
Added value: +9007199254740991
```
- changedInput schema / properties / buildingId / type
```
Previous value: -"number"New value: +"integer"
```
- 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 / startAt / maximum
```
Added value: +9007199254740991
```
- addedInput schema / properties / startAt / minimum
```
Added value: +0
```
- changedInput schema / properties / startAt / type
```
Previous value: -"number"New value: +"integer"
```
First observedv3.2.1Sep 27, 2026

TDQS

B3.1/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 no behavioral context beyond the annotations – no pagination behavior, default limits, or what the compact/full view does, all of which the schema alone carries. With the low bar set by annotations, it still contributes almost nothing of its own.

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, front-loaded sentences with no filler or repetition. It is tight, though the sparseness is arguably under-specification rather than disciplined concision for a 7-parameter tool.

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

Completeness2/5

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

For a 7-parameter list tool with no output schema, the description covers only one optional filter and omits pagination defaults, the search/orderBy combination, and the compact-vs-full view tradeoff. Annotations are minimal, so the description should carry more of this burden than it does.

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 every parameter including view, limit, startAt, search and orderBy is already documented in the schema. The description merely restates the buildingId filter, adding no syntax or interaction detail, 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+resource ('List iOffice floors'), which is enough to distinguish it from the singular io_get_floor sibling by plurality alone. However, it doesn't explicitly name or contrast with the get/create/update/delete floor siblings, so the differentiation is inferred 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 Guidelines3/5

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

'Optionally filter by building ID' implies one usage mode, and the collection noun implies it's for enumerating floors rather than fetching one. But there is no explicit when-to-use guidance, no mention of when to prefer io_get_floor, and no note about combining search/limit/orderBy filters.

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

Deploy Server