Skip to main content
Glama

Get a Kong entity

kong_get

Retrieve a single Kong entity by its ID or unique name through the Admin API. Works with services, routes, consumers, plugins, upstreams, and more.

Instructions

Fetch a single entity by id or name (GET //). Many Kong entities accept either their UUID or their unique name/slug as the id.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesThe entity's id (UUID) or unique name/slug.
entityYesThe Admin API collection path. Plain entity name (e.g. 'services', 'routes', 'consumers', 'plugins', 'upstreams', 'certificates') or a nested collection path (e.g. 'upstreams/my-upstream/targets', 'services/my-service/routes', 'consumers/bob/key-auth'). Common values: services, routes, consumers, consumer_groups, plugins, upstreams, certificates, ca_certificates, snis, vaults, keys, key-sets, workspaces, acls, tags, upstreams/<upstream>/targets, services/<service>/routes, services/<service>/plugins, routes/<route>/plugins, consumers/<consumer>/plugins, consumers/<consumer>/key-auth, consumers/<consumer>/basic-auth, consumers/<consumer>/jwt, consumers/<consumer>/hmac-auth, consumers/<consumer>/acls, rbac/roles, rbac/users, admins, groups, event-hooks, developers.
workspaceNoEE workspace to scope this request to. Overrides the configured default workspace. Leave empty for OSS or the 'default' workspace.
Behavior3/5

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

No annotations are provided, so the description carries the burden. It indicates a read operation ('Fetch'), but doesn't disclose any behavioral traits like authentication requirements, rate limiting, or error handling. The description adds no additional behavioral context beyond the basic action.

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?

The description is a single sentence that efficiently conveys the core purpose and key detail about id flexibility. No redundant words; everything earns its place.

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?

Given 3 parameters with full schema coverage and no output schema, the description is adequate for a simple GET operation. It doesn't describe the response format or error cases, but the tool's simplicity doesn't demand more. Context signals confirm no nested objects or complex output.

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?

The schema covers 100% of parameters, each with descriptions. The description adds value by clarifying that the 'id' can be a UUID or unique name/slug, and the 'entity' parameter is elaborated with common collection paths. This extra context helps the agent use the parameters correctly.

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?

The description clearly states 'Fetch a single entity by id or name' and includes the HTTP method and endpoint pattern, making the purpose immediately obvious. It differentiates from sibling tools like kong_list (which lists multiple) and kong_create/update/delete (which modify).

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

Usage Guidelines3/5

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

No explicit guidance on when to use this tool vs alternatives. It implies it's for fetching a known entity, but doesn't exclude kong_get_config or kong_request, nor does it specify prerequisites or when not to use it.

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/Monohitoxx/kongapigateway-mcp-server'

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