Skip to main content
Glama
jameshgordy

Snipe-IT MCP Server

by jameshgordy

manage_groups

Destructive

Create, retrieve, list, update, and delete Snipe-IT permission groups to control user access rights.

Instructions

Manage Snipe-IT permission groups with CRUD operations.

Groups are used to manage permissions for multiple users at once. Users can belong to multiple groups, and permissions are cumulative.

Actions:

  • create: Create a new group (requires group_data with name)

  • get: Retrieve a single group by ID

  • list: List groups with optional pagination and filtering

  • update: Update an existing group (including permissions)

  • delete: Delete a group

Returns: dict: Result of the operation including success status and data

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoNumber of results to return (for list action)
actionYesThe action to perform on groups
offsetNoNumber of results to skip (for list action)
searchNoSearch query (for list action)
group_idNoGroup ID (required for get, update, delete)
group_dataNoGroup data (required for create, optional for update)

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Behavior3/5

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

The annotations already indicate destructive behavior (destructiveHint=true), and the description mentions the delete action. It adds useful context about cumulative permissions, but does not disclose potential side effects of deletion (e.g., effects on users) or any other operational details beyond what annotations provide.

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?

The description is well-structured and concise, using a clear intro, context sentence, bullet-point action list, and return type. Every sentence adds value and there is no redundancy.

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?

The tool has a full schema, annotations, and an output schema, so the description does not need to explain return values. It clearly lists all actions and their key parameters, making it fairly complete. Minor gaps remain around edge cases like deletion side effects, but overall it is sufficient for a CRUD tool.

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?

All parameters are covered in the schema (100% coverage), so the baseline is 3. The description adds little beyond the schema, only restating that group_data is required for create and that update can modify permissions. No additional semantics are provided.

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?

The description clearly states the tool manages Snipe-IT permission groups with CRUD operations, and the explicit action list (create, get, list, update, delete) leaves no ambiguity about the resource and operations. It distinguishes from sibling tools by focusing specifically on permission groups.

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?

The description provides context about groups ('used to manage permissions for multiple users at once') and notes that permissions are cumulative, which implies when this tool is relevant. However, it does not explicitly compare with alternatives like manage_users or state when not to use this tool.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/jameshgordy/snipeit-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server