garoon-mcp-server

Garoon Get Bulletin Categories

garoon-get-bulletin-categories

Read-only

Retrieve bulletin board categories from Garoon and browse sub-categories by parent ID. Use special IDs for root, pending approval, or drafts.

Instructions

Get bulletin board categories from Garoon. Use parentId to browse sub-categories. Special values: 1=root (default), -1=pending approval, -2=drafts.

Input Schema

TableJSON Schema

Name	Required	Description
`limit`	No	Maximum number of categories to return (1-1000, default: 100)
`offset`	No	Number of categories to skip from the beginning (default: 0)
`parentId`	No	Parent category ID. Special values: 1=root (default), -1=pending approval, -2=drafts

Output Schema

TableJSON 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.

Changed2 schema fields changedv1.3.0Oct 16, 2026
- removedOutput schema / properties / result / properties / categories / items / properties / description / anyOf
```
Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
```
- addedOutput schema / properties / result / properties / categories / items / properties / description / type
```
Added value: +[
+  "string",
+  "null"
+]
```

Changed4 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"

changedOutput schema / properties / result / properties / categories / items / properties / id / description

Previous value: -"Category unique identifier as a numeric string (e.g., 12345)"New value: +"Category identifier as a numeric string. Special categories use negative values: -1=pending approval, -2=drafts"

changedOutput schema / properties / result / properties / categories / items / properties / id / pattern
```
Previous value: -"^\\d+$"New value: +"^(?:-[12]|\\d+)$"
```

First observedv1.1.0Jul 7, 2026

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=false, so the safe-read profile is covered by structured data. The description adds the parentId special-value semantics but says nothing about pagination, total counts, or return behavior beyond what annotations and the output schema carry.

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?

Three short sentences with zero filler; the core action is front-loaded and the parentId guidance follows immediately. Every sentence earns its place.

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?

With an output schema present, return values need not be described, and the read-only annotations cover the safety profile. The description is complete for invocation, missing only cross-tool routing context that a sibling-heavy toolset would benefit from.

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 limit, offset, and parentId, including the same 1/-1/-2 special values. The description merely repeats the parentId values rather than adding format or interpretation beyond the schema, making 3 the correct baseline.

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 (bulletin board categories) tied to Garoon, which is enough to tell it apart from siblings like garoon-get-bulletin-topics. It stops short of explicitly naming the closest sibling, so it is clear but not maximally differentiated.

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?

It gives one concrete usage instruction ('Use parentId to browse sub-categories'), which implies how to traverse the hierarchy, but offers no guidance on when to reach for this tool versus garoon-get-bulletin-topics or garoon-get-bulletin-topic. Usage is implied rather than stated.

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

Deploy Server