Skip to main content
Glama
Sign In
iOffice MCP

iOffice MCP

by chrischall
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

io_get_space

Read-only

Retrieve a single iOffice space or room by its numeric ID. Use the view option to return compact details or the full payload.

Instructions

Get a single iOffice space (room) by ID.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

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

Input Schema

NameRequiredDescriptionDefault
idYesSpace ID
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.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv3.2.6
    • addedInput schema / properties / id / exclusiveMinimum
      Added value: +0
    • addedInput schema / properties / id / maximum
      Added value: +9007199254740991
    • changedInput schema / properties / id / type
      Previous value: -"number"New value: +"integer"
  2. First observedv3.2.1

TDQS

A3.6/5.0
Behavior3/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 and the bar is lower. The description adds only the 'single resource' scope; it says nothing about behavior on a missing/invalid ID or about the compact-vs-full response shape, which is the most consequential behavior here and is left entirely to the schema.

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?

One short sentence, front-loaded with verb and resource, with no filler or redundancy. Nothing could be trimmed without losing content.

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 read-by-ID tool with full schema coverage, no output schema, and annotations covering safety, the description is nearly sufficient. The only meaningful gap is that the compact/full response shape, the tool's main decision point, is never surfaced in the description.

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%, and the 'view' parameter already carries an unusually thorough description in the schema, so the baseline is 3. The description itself adds no meaning about 'id' or 'view' beyond what the schema states.

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 ('Get') and resource ('iOffice space (room)') with the lookup key ('by ID'), which cleanly separates it from io_list_spaces and the other io_get_* siblings. It stops short of explicitly naming an alternative, but the singular 'single ... by ID' framing makes the distinction inferable.

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?

Usage is only implied: an agent infers it should call this when it already has a space ID, versus io_list_spaces when it does not. There is no explicit when-to-use, when-not-to-use, or named alternative, so it sits at the minimum-viable level.

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