Skip to main content
Glama
Sign In
mackerelio-labs

Mackerel MCP Server

Official
by mackerelio-labs
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

List HTTP Server Statistics

list_http_server_stats
Read-only

Retrieve HTTP server statistics from Mackerel to analyze slow endpoints, high-traffic routes, error rates, and API performance by service, time range, method, and route.

Instructions

Retrieve HTTP server statistics from Mackerel.

šŸ” USE THIS TOOL WHEN USERS:

  • Analyze slow HTTP endpoints

  • Identify high-traffic routes

  • Monitor error rates for HTTP requests

  • Investigate API performance issues

Filter by environment and version

list_http_server_stats(
  serviceName="my-service",
  from=1700000000,
  to=1700001800,
  environment="production",
  version="v1.2.3"
)

Filter by HTTP method and route

list_http_server_stats(
  serviceName="my-service",
  from=1700000000,
  to=1700001800,
  method="GET",
  route="/api/users"
)

Pagination

list_http_server_stats(
  serviceName="my-service",
  from=1700000000,
  to=1700001800,
  page=2,
  perPage=50
)

Input Schema

NameRequiredDescriptionDefault
toYesEnd time for retrieving statistics (Unix epoch seconds). The range between `from` is limited to 30 minutes
fromYesStart time for retrieving statistics (Unix epoch seconds). The range between `to` is limited to 30 minutes
pageNoPage number (starting from 1). Default is 1
routeNoFilter by route (partial match). Corresponds to `http.route`, `url.path`, `http.target`, or `http.url` in OpenTelemetry semantic conventions. Preferred in this order
methodNoFilter by HTTP method. Corresponds to `http.request.method` or `http.method` in OpenTelemetry semantic conventions. `http.request.method` is preferred
perPageNoNumber of items per page (1-100). Default is 20
versionNoVersion. Corresponds to `service.version` in OpenTelemetry semantic conventions
environmentNoEnvironment name. Corresponds to `deployment.environment` or `deployment.environment.name` in OpenTelemetry semantic conventions
orderColumnNoSort column. One of `SUM` (total latency), `AVERAGE` (average latency), `P95` (95th percentile latency), `ERROR_RATE` (error rate percentage), or `REQUEST_COUNT` (request count). Default is `P95`
serviceNameYesService name. Corresponds to `service.name` in OpenTelemetry semantic conventions
orderDirectionNoSort order. Either `ASC` (ascending) or `DESC` (descending). Default is `DESC`
serviceNamespaceNoService namespace. Corresponds to `service.namespace` in OpenTelemetry semantic conventions

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.10.0

TDQS

A3.5/5.0
Behavior3/5

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

readOnlyHint=true already tells the agent this is a safe read, so the description only needs to add context. It omits the most operationally important constraint, the 30-minute maximum time range, which lives only in the schema, and says nothing about pagination behavior or result ordering semantics beyond example arguments.

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

Conciseness3/5

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

Purpose and use cases are front-loaded correctly, but the four examples repeat the same serviceName/from/to boilerplate and spend significant space restating what the schema already declares. A single example plus prose about pagination and sorting would be tighter.

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?

For a 12-parameter, no-output-schema tool that returns statistics, the description should at least indicate the shape of the returned metrics (latency, error rate, request counts) and reinforce the time-window and sort defaults. The sketch of use cases plus examples is adequate to invoke it, but leaves genuine gaps.

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 every parameter, enum, and the 30-minute limit is already documented in structured fields. The examples do show useful parameter combinations (environment+version, method+route, page+perPage), but they add no semantics the schema lacks, which is the expected baseline-3 case.

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

Purpose4/5

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

States a specific verb and resource ('Retrieve HTTP server statistics from Mackerel'), so the agent knows exactly what data comes back. It does not distinguish itself from conceptually adjacent siblings such as list_db_query_stats or get_service_metrics.

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

Usage Guidelines4/5

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

The bulleted 'USE THIS TOOL WHEN USERS' list gives clear analytical scenarios (slow endpoints, high-traffic routes, error rates, API performance). It never names an alternative tool or states when not to use this one, so routing against siblings is left implicit.

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