Skip to main content
Glama
Jackson-DM

msp-tools-mcp

by Jackson-DM
OverviewSchemaRelated ServersScoreDiscussions
Python
Local

search_tickets

Read-onlyIdempotent

Search and filter tickets in the Summit Managed IT queue by status, priority, tier, category, client, or free-text query. Returns compact summaries of matching tickets, newest first.

Instructions

Find tickets in the Summit Managed IT queue using filters.

Returns compact summaries (no ticket body) ranked newest-first, capped at limit. Combine filters freely; they AND together. Omit them all to see the newest open work.

WHAT IT DOES NOT DO

  • Does not return ticket bodies. Call get_ticket for the full text of a specific ticket once you have narrowed to one.

  • Does not search inside ticket bodies for topics reliably — query matches subject and body substrings only, with no ranking or synonyms. For "what is our procedure for X", use search_kb instead; that searches the knowledge base, which is where procedure lives.

  • Does not classify anything. The category it returns is the as-filed intake label typed by whoever opened the ticket. It is frequently wrong. Do not use it to conclude a ticket is safe or routine.

FILTER VALUES status open | pending | resolved priority low | medium | high | critical tier 1 | 2 | 3 category password_account, email, network_vpn, hardware, software_licensing, security, server_outage, onboarding_offboarding client client company name, case-insensitive substring query free-text substring over subject and body

ERRORS This tool does not fail on an empty result. total_matched: 0 with an empty list means nothing matched — widen the filters rather than retrying the same call. truncated: true means more matched than were returned; narrow the filters to see the remainder.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
tierNo
limitNo
queryNo
clientNo
statusNo
categoryNo
priorityNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
okNo
messageNo
ticketsNo
returnedYes
truncatedYesTrue when total_matched exceeded limit; narrow the filters to see the rest.
error_codeNo
total_matchedYesTickets matching the filters before the cap.

Tool Definition Quality

A5/5.0
Behavior5/5

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

Discloses limitations: no ticket bodies, unreliable classification, query matching only substrings without ranking. Explains error handling (empty result vs truncated). Annotations already readOnly, idempotent; description adds behavioral context beyond annotations.

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?

Well-structured with clear sections: what it does, what it does not do, filter values, errors. No redundant sentences, efficient and thorough.

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

Completeness5/5

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

Covers all aspects: filtering, ordering, limits, return format (compact summaries, total_matched, truncated), and error conditions. Output schema exists so return values are not required, but description still explains them. Fully adequate for this complex tool.

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

Parameters5/5

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

Despite 0% schema coverage, description provides detailed filter values and allowed enums for each parameter (status, priority, tier, category, client, query). Adds meaning that the bare schema (type, default) lacks.

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?

Clearly states it finds tickets in Summit Managed IT queue using filters. Distinguishes from siblings get_ticket (full text) and search_kb (procedures). Explicit about what it does not do.

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

Usage Guidelines5/5

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

Provides explicit when-to-use and when-not-to-use scenarios, including alternatives like get_ticket for full text and search_kb for procedures. Explains filter combination (AND) and empty result behavior.

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/Jackson-DM/msp-tools-mcp'

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