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

the-real-snipeit-mcp

by mguttmann
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

List consumables

snipeit_list_consumables
Read-onlyIdempotent

Retrieve a paginated list of consumables from Snipe-IT, filtered by search text, company, category, or manufacturer, with optional auto-pagination for larger result sets.

Instructions

GET /consumables: paginated list. Supports search and common filters.

Input Schema

NameRequiredDescriptionDefault
allNoIf true, auto-paginate up to 10,000 rows or until the result size cap; if the cap is hit the result has truncated: true and next_offset to continue with limit/offset
limitNoPage size (default 50, max 500)
offsetNo
searchNo
company_idNo
category_idNo
manufacturer_idNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.2

TDQS

B3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint, and destructiveHint=false. The description adds that the result is paginated and searchable, but does not explain truncation behavior, next_offset usage, authentication needs, or rate limits beyond what the schema already states.

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?

Two short sentences, front-loaded with the endpoint and pagination behavior. There is no redundant or wasted text, even though 'common filters' is vague.

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?

For a 7-parameter list tool with no output schema and many sibling consumable-related endpoints, this definition is too sparse. It does not specify which filters are available, what the response contains, or why an agent should choose it over sibling listing tools.

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

Parameters2/5

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

Schema description coverage is only 29%; only 'all' and 'limit' are described in the schema. The description's phrase 'common filters' does not identify company_id, category_id, manufacturer_id, offset, or search semantics, so it fails to compensate for the low schema coverage.

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?

Names the resource (consumables) and the operation (GET /consumables: paginated list), so the core purpose is clear. However, it does not distinguish this from sibling tools such as snipeit_gen_consumables_1, snipeit_list_accessories, or snipeit_list_components.

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?

The description gives no guidance on when to use this tool versus the many other consumables/listing endpoints. It also provides no exclusions, prerequisites, or conditions for choosing this over snipeit_gen_consumables_1 or snipeit_raw_request.

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