Skip to main content
Glama

Get service setup eligibility

get_service_setup_eligibility
Read-only

Which managed services one application environment can set up right now: for each catalogue package version and mode, available, blocked with the reason and the fix (it does not deploy through the Ankra native engine, a playground is short of capacity, Ankra-hosted is not available, a permission is missing, the application is not deployed to that namespace, credentials are needed, ...), or unknown when the cluster's capacity cannot be established. It runs prepare_service_setup's checks on the environment's own cluster with default settings and records nothing; the service name is the one check left to the prepare. Use it before prepare_service_setup to pick a package and mode that can go through. 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>",
      "cluster_id": "<cluster_id>",
      "namespace": "<namespace>"
    },
    "name": "get_service_setup_eligibility"
  }
}

Input Schema

NameRequiredDescriptionDefault
afterNonext_cursor from the previous page, to read the next one.
limitNoPackage versions per page, 1-25. Defaults to 10.
namespaceYesThe namespace the application deploys to on that cluster.
cluster_idYesThe cluster the environment deploys to (UUID); the service is checked there.
application_idYesApplication id (UUID) from list_applications.
package_version_idNoCheck this package version only (UUID from list_service_packages).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, and the description adds real context beyond that: it runs prepare_service_setup's checks with default settings, records nothing, and checks capacity on the environment's own cluster. The enumeration of blocked reasons (native engine, playground capacity, missing permission, undeployed namespace, credentials) tells the agent what the failure surface looks like, though the trailing 'Read-only.' merely repeats the annotation.

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?

The core statement is front-loaded, but the definition is a single dense block of clauses and parenthetical enumerations (including an open-ended '...') that make it slower to parse than needed. Several qualifiers could be tightened without losing meaning.

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 and a read-only check tool, the description carries the burden of describing results, and it does: three outcome states plus the reason-and-fix payload for blocked cases. It is nearly complete; what's missing is any hint about result volume or how pagination interacts with the per-package-version results.

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 the schema already documents all six parameters including the package_version_id filter and pagination cursor. The description's phrasing ('for each catalogue package version and mode') loosely frames the pagination and filter, but adds no format, default, or interaction detail beyond the schema. Baseline 3 applies.

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: reports which managed services an application environment can set up right now, enumerating available/blocked/unknown outcomes per catalogue package version and mode. It also draws an explicit boundary against prepare_service_setup (which checks remain to that tool), so an agent can distinguish it from the sibling without opening either 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 clear sequencing guidance: use it before prepare_service_setup to pick a package and mode that can go through, and notes the service name is the one check left to the prepare. It names the alternative and the condition that selects it, but offers no explicit when-not or cost/precondition caveats beyond that.

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.