No user-submitted related servers found.
Scored across 27 tools
Most tools map cleanly to a resource+action (list/get per entity, CRUD for log parsing rules), so selection is usually obvious. The main friction points are get_application_metrics vs get_application_metric_data (metadata vs time-series data is only inferable from descriptions) and the three log-parsing-rule tools (create/update/test/generate) whose boundaries overlap somewhat. query_nrql vs nerdgraph_query are distinguishable by query language but could be mispicked by a naive agent.
Nearly everything follows a predictable snake_case verb_noun pattern (list_applications, get_dashboard, update_dashboard, create_log_parsing_rule). Deviations are minor: query_nrql and nerdgraph_query drop the verb-first ordering, and manage_credentials is a single tool multiplexing status/store/delete via an action parameter rather than following the one-verb-per-tool convention.
27 tools is heavy and pushes past the comfortable range, though it is partly justified by the broad surface (APM, alerts, synthetics, dashboards, infrastructure, users, logs, credentials, ad-hoc querying). Some redundancy exists — dual metric tools, dual query tools, and four log-parsing-rule tools — plus a multi-action credentials tool that could be split or trimmed. It is defensible but not tight.
Log parsing rules have full CRUD plus test/generate, and deployments/applications/dashboards cover their core lifecycles. However, many resources are read-only stubs — alert policies, synthetic monitors, servers, and users only support list/get, and dashboards lack create/delete — leaving noticeable gaps for common workflows. Ad-hoc NRQL/NerdGraph querying partially compensates by providing an escape hatch.