garoon-mcp-server

Get Facilities In Group

garoon-get-facilities-in-group

Read-only

Retrieve facilities that belong to a specific facility group, with optional limit and offset controls for paginated results.

Instructions

Get facilities that belong to a specific facility group with optional limit and offset parameters.

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": {
      "facilityGroupId": "<facilityGroupId>"
    },
    "name": "garoon-get-facilities-in-group"
  }
}

Input Schema

Name	Required	Description
`limit`	No	Maximum number of facilities to return (1-1000, default: 100)
`offset`	No	Number of facilities to skip from the beginning (default: 0)
`facilityGroupId`	Yes	Facility group ID to list facilities for (numeric string)

Output Schema

Name	Required	Description
`error`	No	Error message. Present on error
`result`	No	Result of the operation. Present on success
`status`	No	HTTP status code from the Garoon API. Present only when the error is an HTTP error response
`responseText`	No	Raw response body from the Garoon API. Present only when the error is an HTTP error response

Schema Changelog

Changes observed during successful MCP inspections.

Changed5 schema fields changedv1.3.0Oct 16, 2026

addedOutput schema / properties / result / properties / facilities / items / additionalProperties
```
Added value: +false
```

removedOutput schema / properties / result / properties / facilities / items / allOf

Removed value: -[
-  {
-    "additionalProperties": false,
-    "properties": {
-      "code": {
-        "description": "Facility code (e.g., '101', '202')",
-        "type": "string"
-      },
-      "id": {
-        "description": "Facility unique identifier as a numeric string (e.g., 12345)",
-        "pattern": "^\\d+$",
-        "type": "string"
-      },
-      "name": {
-        "description": "Facility name (e.g., 'Conference Room 1', 'Meeting Room 2')",
-        "type": "string"
-      },
-      "notes": {
-        "description": "Notes about the facility",
-        "type": "string"
-      }
-    },
-    "required": [
-      "id",
-      "code",
-      "name"
-    ],
-    "type": "object"
-  },
-  {
-    "additionalProperties": false,
-    "properties": {
-      "facilityGroup": {
-        "description": "ID of the facility group this facility belongs to",
-        "pattern": "^\\d+$",
-        "type": "string"
-      }
-    },
-    "required": [
-      "facilityGroup"
-    ],
-    "type": "object"
-  }
-]

addedOutput schema / properties / result / properties / facilities / items / properties

Added value: +{
+  "code": {
+    "description": "Facility code (e.g., '101', '202')",
+    "type": "string"
+  },
+  "facilityGroup": {
+    "description": "ID of the facility group this facility belongs to",
+    "pattern": "^\\d+$",
+    "type": "string"
+  },
+  "id": {
+    "description": "Facility unique identifier as a numeric string (e.g., 12345)",
+    "pattern": "^\\d+$",
+    "type": "string"
+  },
+  "name": {
+    "description": "Facility name (e.g., 'Conference Room 1', 'Meeting Room 2')",
+    "type": "string"
+  },
+  "notes": {
+    "description": "Notes about the facility",
+    "type": "string"
+  }
+}

addedOutput schema / properties / result / properties / facilities / items / required
```
Added value: +[
+  "id",
+  "code",
+  "name",
+  "facilityGroup"
+]
```
addedOutput schema / properties / result / properties / facilities / items / type
```
Added value: +"object"
```

Changed2 schema fields changedv1.2.0Aug 21, 2026

changedInput schema / $schema

Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"

changedOutput schema / $schema

Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"

First observedv1.1.0Jul 7, 2026

TDQS

A3.5/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds essentially nothing beyond that, merely alluding to pagination, and omits auth requirements or behavior on invalid group IDs, so a baseline 3 is warranted.

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?

One front-loaded sentence with the resource and scope stated first. The trailing clause about limit/offset is redundant with the schema, a minor waste, but the whole thing is short and readable.

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?

An output schema exists, so return values need no explanation, and all three parameters are fully schema-documented. The only gap is how to obtain a valid facilityGroupId, which is left implicit.

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 coverage is 100% and each parameter is documented with defaults and bounds, so the schema carries the meaning. The description only restates that limit/offset exist as optional, adding no new semantics beyond the schema.

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 ('facilities') scoped to 'a specific facility group', which distinguishes it from the sibling garoon-get-facilities (all facilities) by narrowing to a group. It never names the alternatives explicitly, but the scope is unambiguous.

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: the required facilityGroupId suggests the caller must first know a group ID (e.g., from garoon-get-facility-groups), but the description states no when-to-use condition or contrast with garoon-get-facilities/get-facility-groups.

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

Deploy Server