Related Servers

The tool set is heavily redundant with many near-duplicate operations, such as multiple variants for getting forms (e.g., get_a_form_in_a_plan, get_a_form_in_a_plan_nested), aliases like get_form_response_options and get_form_response_options_alias, and separate update shift tools (update_a_shift vs update_a_shift_by_id). This makes it extremely difficult for an agent to select the correct tool, as many appear to perform the same function with slight variations.

While the prefix 'xmatters_' and verb_noun structure is generally followed, there are significant inconsistencies: mixed use of 'get_a' vs 'get', 'modify' vs 'update', and 'create' vs 'add'. Additionally, some names contain encoded characters like '39' (e.g., get_a_group_39_s_recipients), and there are aliases with suffixes like '_alias' and '_nested' that deviate from a clear pattern. The naming is not chaotic but is inconsistent enough to confuse.

With 179 tools, this server exposes an overwhelming number of operations, far beyond the typical 3-15 tools for an MCP server. This appears to be a direct dump of the entire xMatters API, including duplicated and variant endpoints, which is excessive for an agent to navigate effectively. The count severely violates the principle of a well-scoped tool set.

The server covers a wide range of domain resources with CRUD operations for people, groups, sites, plans, services, shifts, and more, including uploads and triggers. However, there are notable gaps: no delete operations for forms, scenarios, or some other entities, and some lifecycle steps are missing (e.g., no delete for scenarios). While the coverage is extensive, these gaps prevent a perfect score.