Skip to main content
Glama
the-real-snipeit-mcp

the-real-snipeit-mcp

PATCH /licenses/{id}/seats/{seat_id}

snipeit_gen_licensesidseatsseat_id_2
DestructiveIdempotent

Update a license seat's checkout to assign it to a user or asset, or modify the existing seat assignment and note.

Instructions

PATCH /licenses/{id}/seats/{seat_id}: Update user or asset a license is checked-out to (Check-in/Check-out). Generated from Snipe-IT OpenAPI operation licensesidseatsseat_id-2.

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": {
      "id": "<id>",
      "seat_id": "<seat_id>"
    },
    "name": "snipeit_gen_licensesidseatsseat_id_2"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesThe id (not name) of the license.
bodyNo
confirmNoRequired when SNIPEIT_CONFIRM_WRITES=true. Exact string "YES" to apply this write.
seat_idYesThe Seat ID (unique seat identifier) of the license seat that will be modified

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.2

TDQS

C2.6/5.0
Behavior2/5

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

Annotations already declare destructiveHint=true, idempotentHint=true and openWorldHint=true, so the safety profile is covered. The description adds only that it changes the user/asset assignment; it does not explain that omission of a field may unassign a seat, what the confirm behavior means, or what state changes occur.

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?

Two short sentences with the purpose front-loaded after the path prefix. The 'Generated from Snipe-IT OpenAPI operation...' boilerplate and the repeated title add no information an agent needs.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

This is a destructive, nested-body mutation tool with no output schema and an undocumented nested body schema; the description should clarify the assignment semantics and the confirm gate. As written, an agent must infer all of that from schema fields alone.

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 75%, with id ('not name') and seat_id well documented, so the baseline is 3. The phrase 'user or asset' loosely maps to the undescribed body fields assigned_to and asset_id, adding marginal value, but the nested 'note' field and confirm workflow receive no explanation in the description.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description adds a real purpose beyond the path: 'Update user or asset a license is checked-out to,' which tells the agent it mutates seat assignment. However, it opens by restating the title/path, and '(Check-in/Check-out)' is ambiguous about which direction of change occurs, with no differentiation from the sibling PUT /licenses/{id}/seats/{seat_id} or checkout_license_seat.

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

Usage Guidelines2/5

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

No statement of when to use this PATCH versus the PUT sibling or the dedicated checkout_license_seat tool, and no prerequisites mentioned. The only hint is the parenthetical '(Check-in/Check-out)', which is not actionable guidance.

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

Deploy Server

Other Tools