Skip to main content
Glama
jameshgordy

Snipe-IT MCP Server

by jameshgordy

manage_manufacturers

Destructive

Create, retrieve, list, update, and delete manufacturer records in Snipe-IT to manage companies that produce assets.

Instructions

Manage Snipe-IT manufacturers with CRUD operations.

Manufacturers represent the companies that produce assets.

Operations:

  • create: Create a new manufacturer (requires manufacturer_data with name)

  • get: Retrieve a single manufacturer by ID

  • list: List manufacturers with optional pagination and filtering

  • update: Update an existing manufacturer (requires manufacturer_id and manufacturer_data)

  • delete: Delete a manufacturer (requires manufacturer_id)

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 manufacturers
offsetNoNumber of results to skip (for list action)
searchNoSearch query (for list action)
manufacturer_idNoManufacturer ID (required for get, update, delete)
manufacturer_dataNoManufacturer 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 readOnlyHint=false, and the description adds the CRUD operation breakdown and return format. It does not disclose additional behavioral details such as cascading deletes, authentication requirements, or partial update semantics, so it only partially supplements the annotations.

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 front-loaded, with a clear purpose, context, bulleted operations, and a returns section. Every sentence adds value without unnecessary filler.

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 an 8-parameter CRUD tool, the description covers all actions and their required parameters, and the output schema handles return details. It lacks guidance on when to use alternatives and error handling, but overall it is sufficiently complete for selecting and invoking the tool.

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%, but the description adds valuable nuance by stating that create requires manufacturer_data with name, which is not explicit in the schema's optional name field. It also summarizes list filtering and pagination, making parameter usage clearer.

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?

The description clearly states that the tool manages Snipe-IT manufacturers with CRUD operations and enumerates specific actions. It is unambiguous about the resource and actions, though it doesn't explicitly differentiate from sibling tools like manage_suppliers.

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 per-action usage details and required parameters, implying when to use the tool. However, it doesn't explicitly mention when not to use it or point to alternatives (e.g., manage_suppliers for suppliers), so the guidance is only implied rather than explicit.

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