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

the-real-snipeit-mcp

by mguttmann
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

GET /reports/activity

snipeit_gen_reportsactivity
Read-onlyIdempotent

Retrieves Snipe-IT activity report entries with filters for action type, item, target, and user, plus sorting, search, and pagination to audit asset history.

Instructions

GET /reports/activity. Generated from Snipe-IT OpenAPI operation reportsactivity.

Input Schema

NameRequiredDescriptionDefault
sortNoWhat column the results should be sorted by (defaults to created_at date if no value is given)
limitNoSpecify the number of results you wish to return. Defaults to 50, but we have it set to 2 by default so the API explorer doesn't scroll forever.
orderNoAscending or descending order (defaults to desc if no value is given)
offsetNoThe offset from the start of results to use in order to page through the result set
searchNoString to search on
item_idNoThe ID of the item you're querying against. Required if passing item_type
item_typeNoThe type of item you're searching against. `App\Models\Asset`, etc. Required when passing item_id.
target_idNoThe ID of the target you're querying against. Required if passing target_type
action_typeNoThe action type you'e querying against. Example values here are: "add seats", "checkin from", "checkout", "update"
target_typeNoThe type of target (entity something is checked out to) you're searching against. `App\Models\User`, etc. Required when passing target_id.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.2

TDQS

D1.9/5.0
Behavior2/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint, and destructiveHint=false, so the safety profile is covered externally. The description adds no behavioral context such as pagination defaults, filtering semantics, or what the activity report returns.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is short but under-specified rather than concise. The second sentence about generation adds no decision-relevant value and displaces information an agent actually needs.

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

Completeness1/5

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

For a ten-parameter reporting endpoint with no output schema, the description is completely inadequate. It omits purpose, return behavior, and guidance on the rich filtering options exposed in the schema.

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%, so the schema fully documents the ten parameters. The description contributes no additional parameter meaning beyond the schema, which is acceptable but not helpful.

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

Purpose2/5

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

The description only restates the tool path ('GET /reports/activity') and notes it was generated from an OpenAPI operation. It does not explain what an activity report contains or how it differs from sibling report and list tools.

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

Usage Guidelines1/5

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

There is no guidance on when to use this tool, when not to use it, or which sibling tools cover related reporting needs. The agent is left to infer everything from the name.

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