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

the-real-snipeit-mcp

GET /licenses/{id}/seats/{seat_id}

snipeit_gen_licensesidseatsseat_id
Read-onlyIdempotent

Fetches details for one specific seat under a license using the license ID and unique seat ID, so you can inspect seat assignment data.

Instructions

GET /licenses/{id}/seats/{seat_id}: Get details for one specific unique Seat ID for a particular license. Generated from Snipe-IT OpenAPI operation licensesidseatsseat_id.

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

Input Schema

NameRequiredDescriptionDefault
idYesThe id (not name) of the license.
seat_idYesThe Unique Seat ID for this seat for this license

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.2

TDQS

B3.3/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, and openWorldHint=true. The description adds only a generated-from-OpenAPI note and does not disclose additional behavior such as authentication needs, response shape, or error conditions.

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 purpose is front-loaded in a single sentence. The trailing 'Generated from Snipe-IT OpenAPI operation...' boilerplate is unnecessary but brief, so the description remains appropriately sized.

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 a simple read-only GET of one license seat, annotations and a fully documented input schema cover the essential context. The description does not explain return values, but no output schema exists and the operation is straightforward enough that this omission is minor.

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%, and the schema already explains that 'id' is the license ID (not name) and 'seat_id' is the unique seat ID for that license. The description adds no parameter meaning beyond the schema, so the baseline of 3 is appropriate.

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 states a specific verb and resource: 'Get details for one specific unique Seat ID for a particular license.' It distinguishes retrieval of a single seat from broader seat-listing operations, though it does not explicitly name the sibling tools it differs from.

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?

Usage is implied: the tool is for fetching one seat when both a license ID and a seat ID are known. There is no explicit guidance about when to prefer this over snipeit_get_license_seats, snipeit_gen_licensesidseats, or snipeit_gen_licensesidseatsseat_id_2.

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