iOffice MCP

io_list_buildings

Read-only

List iOffice buildings with search, pagination, and sorting to browse or locate facility records by name or description.

Instructions

List iOffice buildings. Supports search, pagination, and sorting.

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

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 or description
`orderBy`	No	Property to sort by (default: id)
`startAt`	No	Pagination offset (default 0)
`orderByType`	No	Sort direction (default: asc)

Schema Changelog

Changes observed during successful MCP inspections.

Changed6 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 / 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.4/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 that—no auth needs, rate limits, or response behavior—so it does not exceed the annotation baseline.

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, front-loaded with the core action and followed by a compact capability summary. No filler, redundancy, or buried information.

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?

For a simple list tool with a fully documented schema and annotations covering safety, the description is adequate for correct invocation. It could mention when to prefer it over io_get_building, but nothing critical is missing.

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 descriptions cover 100% of the six parameters, including defaults, bounds, and enum meanings. The description merely lists search/pagination/sorting, which maps to parameters but adds no semantics beyond what the schema already provides, so the baseline 3 applies.

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

Purpose5/5

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

States a specific verb ('List') and resource ('iOffice buildings'), which clearly distinguishes it from io_get_building and the sibling list tools for floors, spaces, users, etc. An agent can identify what it does without opening the schema.

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 when-to-use guidance or exclusions are given. The sentence 'Supports search, pagination, and sorting' describes capabilities rather than routing conditions, and it never mentions the alternative io_get_building for a single building.

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

Deploy Server