Skip to main content
Glama
advenimus

SyncroMSP MCP Server

tickets_list

Retrieve a paginated list of tickets filtered by customer, status, date, or other criteria.

Instructions

List tickets with optional filters. Returns paginated results.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
customer_idNoFilter by customer ID
contact_idNoFilter by contact ID
numberNoFilter by ticket number
statusNoFilter by status (e.g., 'New', 'In Progress', 'Resolved', 'Waiting for Parts')
queryNoSearch query string
user_idNoFilter by assigned user ID
mineNoOnly show tickets assigned to the authenticated user
resolved_afterNoISO 8601 date - tickets resolved after this date
created_afterNoISO 8601 date - tickets created after this date
since_updated_atNoISO 8601 date - tickets updated after this date
ticket_search_idNoFilter by saved search ID
asset_nameNoReturn only tickets linked (via assets) to assets whose name matches (case-insensitive partial)
asset_serialNoReturn only tickets linked (via assets) to assets whose serial number matches (case-insensitive partial)
pageNoPage number for pagination
Behavior3/5

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

The description mentions pagination but does not disclose that this is a read-only operation (no annotations provided). Adequate for a list tool, but minimal behavioral context.

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?

Single sentence, no waste, front-loaded with purpose.

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

Completeness3/5

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

With 14 optional parameters and no output schema or annotations, the description is too brief. Lacks details on pagination mechanics, default page size, sorting, or returned fields.

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 100%, so the description adds no new parameter information beyond 'optional filters'. Baseline 3 is appropriate.

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 the tool lists tickets with optional filters and returns paginated results, distinguishing it from sibling tools like tickets_get (single ticket) and tickets_list_comments.

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 guidance on when to use this tool versus alternatives. It only implies usage with filters, but fails to mention that for a single ticket, tickets_get should be used, or for comments, tickets_list_comments.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/advenimus/syncromsp-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server