Snipe-IT MCP Server

activity_reports

Read-onlyIdempotent

Retrieve Snipe-IT activity logs and reports. Filter by item, action type, or search query to track checkouts, checkins, and updates.

Instructions

Query Snipe-IT activity logs and reports.

Provides access to the activity log which tracks all actions performed in Snipe-IT including checkouts, checkins, updates, and more.

Actions:

list: List activity records with optional filtering
item_activity: Get activity for a specific item (requires item_type and item_id)

Returns: dict: Activity records matching the query

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": {
      "action": "<action>"
    },
    "name": "activity_reports"
  }
}

Input Schema

Name	Required	Description
`limit`	No	Number of results to return
`action`	Yes	The action to perform
`offset`	No	Number of results to skip
`search`	No	Search query
`item_id`	No	Item ID for item_activity
`item_type`	No	Item type for item_activity (e.g., 'asset', 'license', 'accessory')
`target_id`	No	Filter by target ID
`action_type`	No	Filter by action type (e.g., 'checkout', 'checkin', 'update')
`target_type`	No	Filter by target type (e.g., 'asset', 'license', 'user')

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.6.0Aug 2, 2026

TDQS

A4.1/5.0

Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint false, so the safety profile is well-covered. The description adds meaningful behavioral context beyond annotations by specifying that item_activity requires both item_type and item_id, and by noting the return format (dict). It does not contradict annotations.

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 reasonably concise and well-structured with an intro, action list, and return type. It avoids excessive detail and is front-loaded with the core purpose. Slight redundancy exists in the 'Returns: dict' line, which is already covered by the output schema, but it does not significantly detract.

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 tool with 9 parameters and one required action enum, the description is sufficiently complete. It explains the two modes, the one constraint on item_activity, and the return type. The output schema exists, so the description need not dwell on return details. No critical gaps are evident.

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 parameter description coverage is 100%, so the schema already documents each parameter thoroughly. The description adds minimal extra parameter meaning—only the grouping into actions and the requirement for item_activity. This matches the baseline for high schema coverage.

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 clearly states a specific verb and resource: 'Query Snipe-IT activity logs and reports.' It further breaks down the two primary actions (list and item_activity), which helps distinguish it from sibling tools like audit_tracking or asset_operations.

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 provides clear context for when to use each action: 'list' for general activity records with filtering, and 'item_activity' for a specific item, noting it requires item_type and item_id. However, it does not explicitly mention alternative tools or exclusion criteria, so it stops short of full when-not usage guidance.

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