Skip to main content
Glama
Kong

Kong Konnect MCP Server

Official
by Kong

query_api_requests

Query Kong API Gateway request logs with filters on time, status codes, HTTP methods, services, routes, and consumers. Analyze traffic patterns and performance metrics.

Instructions

Query and analyze Kong API Gateway requests with customizable filters. Before calling this it's necessary to have a controlPlaneID and a serviceID or routeID. These can be obtained using the list-control-planes, list-services, and list-routes tools.

INPUT:

  • timeRange: String - Time range for data retrieval (15M, 1H, 6H, 12H, 24H, 7D)

  • statusCodes: Number[] (optional) - Filter by specific HTTP status codes

  • excludeStatusCodes: Number[] (optional) - Exclude specific HTTP status codes

  • httpMethods: String[] (optional) - Filter by HTTP methods (e.g., GET, POST)

  • consumerIds: String[] (optional) - Filter by consumer IDs

  • serviceIds: String[] (optional) - Filter by service IDs. The format of this field must be ":".

  • routeIds: String[] (optional) - Filter by route IDs. The format of this field must be "controlPlaneID:routeID"

  • maxResults: Number - Maximum number of results to return (1-1000)

OUTPUT:

  • metadata: Object - Contains totalRequests, timeRange, and applied filters

  • requests: Array - List of request objects with details including:

    • requestId: String - Unique request identifier

    • timestamp: String - When the request occurred

    • httpMethod: String - HTTP method used (GET, POST, etc.)

    • uri: String - Request URI path

    • statusCode: Number - HTTP status code of the response

    • consumerId: String - ID of the consumer making the request

    • serviceId: String - ID of the service handling the request

    • routeId: String - ID of the matched route

    • latency: Object - Response time metrics

    • clientIp: String - IP address of the client

    • and many more detailed fields...

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
routeIdsNoFilter by route IDs (from list-routes tool)
timeRangeNoTime range for data retrieval (15M = 15 minutes, 1H = 1 hour, etc.)1H
maxResultsNoNumber of items to return per page
serviceIdsNoFilter by service IDs
consumerIdsNoFilter by consumer IDs
httpMethodsNoFilter by HTTP methods (e.g. ['GET', 'POST', 'DELETE'])
statusCodesNoFilter by specific HTTP status codes (e.g. [200, 201, 404])
excludeStatusCodesNoExclude specific HTTP status codes (e.g. [400, 401, 500])
Behavior3/5

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

No annotations provided. Description notes required format for IDs and default time range, but lacks explicit statements on read-only nature, rate limits, or error handling.

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

Conciseness4/5

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

Well-structured with intro, prerequisites, input/output sections. Minor vagueness in 'and many more detailed fields...' but overall efficient.

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

Completeness4/5

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

No output schema, but description provides detailed output structure. Covers all parameters and dependencies. Lacks edge case and error handling details.

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

Parameters4/5

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

Schema coverage is 100% (baseline 3). Description adds extra context: explains timeRange enum meanings and details the special format for serviceIds/routeIds beyond schema constraints.

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?

Description clearly states the tool queries and analyzes Kong API Gateway requests with customizable filters, distinct from sibling tools that list entities.

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?

Explicitly states prerequisites (controlPlaneID, serviceID/routeID) and references sibling tools to obtain them, providing clear when-to-use guidance.

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/Kong/mcp-konnect'

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