Skip to main content
Glama
jameshgordy

Snipe-IT MCP Server

by jameshgordy

manage_departments

Destructive

Create, retrieve, list, update, and delete departments in Snipe-IT. Manage organizational units assigned to users.

Instructions

Manage Snipe-IT departments with CRUD operations.

Departments are organizational units within a company that can be assigned to users.

Actions:

  • create: Create a new department (requires department_data with name)

  • get: Retrieve a single department by ID

  • list: List departments with optional pagination and filtering

  • update: Update an existing department

  • delete: Delete a department

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

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
sortNoField to sort by (for list action)
limitNoNumber of results to return (for list action)
orderNoSort order (for list action)
actionYesThe action to perform on departments
offsetNoNumber of results to skip (for list action)
searchNoSearch query (for list action)
department_idNoDepartment ID (required for get, update, delete)
department_dataNoDepartment 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?

Annotations already declare destructiveHint=true, and the description aligns by listing a delete action. The description adds a return type note ('dict...') and create requirements ('requires department_data with name'), but doesn't disclose specifics about deletion consequences or other behavioral nuances. With annotations covering the safety profile, this meets the baseline.

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?

The description is well-structured with a clear opening, a brief context sentence, bulleted actions, and a returns section. It is slightly longer than necessary but each section earns its place. No redundant or filler 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?

The description covers CRUD operations, parameter requirements, and return format. Since an output schema exists, it needn't explain return values in detail. It is sufficiently complete for a moderate-complexity CRUD tool, though it could mention pagination/filtering specifics (already in schema) or how department_data interacts with actions.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3. The description adds value by noting that create 'requires department_data with name', which is not enforced in the schema (name is nullable). This clarifies a critical requirement beyond what the structured schema provides.

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 opens with 'Manage Snipe-IT departments with CRUD operations', clearly stating the resource and verb. It then enumerates specific actions (create, get, list, update, delete), which distinguishes it from sibling tools focused on other resources like assets or users.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies usage through its action list, making it clear the tool is for department management. It doesn't explicitly say when to use this over alternatives, but the resource-specific wording and sibling context make that self-evident. Minor deduction for not stating exclusions or alternatives.

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