Skip to main content
Glama

List service consumers

list_service_consumers
Read-only

List one application's consumer bindings (the twin of ankra services consumers list): each names the application namespace on a cluster that a managed service is set up for. A binding's id goes in prepare_service_setup's consumer_ids. Read-only.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "application_id": "<application_id>"
    },
    "name": "list_service_consumers"
  }
}

Input Schema

NameRequiredDescriptionDefault
afterNonext_cursor from the previous page, to read the next one.
limitNoPage size, 1-50. Defaults to 25.
application_idYesApplication id (UUID) from list_applications.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior3/5

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

"Read-only" merely restates the readOnlyHint annotation, so it earns no credit there. It does add real context beyond annotations by explaining what a returned binding represents and how its id is consumed, but nothing about ordering, default page contents, or what happens for an application with no bindings.

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?

Front-loaded with the core action and scope, followed by a compact definition and the downstream-use hint, with no filler. The CLI twin reference ("twin of `ankra services consumers list`") is marginally useful cross-mapping but slightly extraneous for an agent that only calls MCP tools.

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?

With no output schema, the description does the important work of defining what a binding contains and how its id is used, and pagination is fully covered by the schema. It stops short of naming any fields returned per binding, which would round out a list tool with no documented return shape.

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 coverage is 100%, with after/limit/application_id all documented in the schema, so the baseline of 3 applies. The description adds no parameter-level meaning beyond implying the application scoping already in the schema.

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?

States a specific verb and resource with explicit scope ("List one application's consumer bindings") and defines what a binding is: the application namespace on a cluster that a managed service is set up for. An agent can distinguish this from list_service_instances and other list_* siblings without reading the schema.

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?

Gives concrete downstream context: the binding id is what goes into prepare_service_setup's consumer_ids, which tells an agent when to call this before a setup flow. It lacks explicit 'do not use X' routing against the nearest alternative (list_service_instances), so it stops short of full when/when-not guidance.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.