Skip to main content
Glama

List service packages

list_service_packages
Read-only

List the managed-service packages this organisation may set up (the twin of ankra services packages list): PostgreSQL, Valkey, OpenSearch, VictoriaMetrics, VictoriaLogs and the rest of the catalogue, each with its package version id, version and capability. Pass a package_version_id to get_service_package for its parameters and modes, and to prepare_service_setup to set one up. Read-only.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_service_packages"
  }
}

Input Schema

NameRequiredDescriptionDefault
afterNonext_cursor from the previous page, to read the next one.
limitNoPage size, 1-50. Defaults to 25.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/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 reinforces it with 'Read-only' (redundant but harmless). It adds value beyond the annotations by disclosing the shape of each returned item — package version id, version, and capability — which matters since no output schema exists. It does not describe pagination behaviour (how 'after' interacts with cursors or total counts), which is the main remaining gap.

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, then the catalogue examples, then the follow-up routing — a logical order. Slightly dense in one paragraph, and the CLI-twin parenthetical ('the twin of `ankra services packages list`') is only marginally useful to an agent, but the enumeration of package names earns its space by making the scope concrete.

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?

For a two-parameter, read-only list tool with no output schema, the description covers purpose, scope, returned fields, and the two downstream tools. Pagination semantics are left entirely to the schema, which is acceptable given its 100% coverage, but a note on how to iterate pages would have made it complete.

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 both parameters (after, limit with 1-50 bounds and default 25) are already fully documented in the schema; the description adds nothing about them. The 'Pass a package_version_id' sentence refers to a parameter of sibling tools, not this one, so it does not deepen this tool's parameter semantics. Baseline 3 is appropriate.

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 ('List the managed-service packages this organisation may set up') and disambiguates from near-neighbours by naming what it returns (package version id, version, capability) rather than the package's parameters/modes, which belong to get_service_package. The concrete catalogue examples (PostgreSQL, Valkey, OpenSearch, VictoriaMetrics, VictoriaLogs) plus the CLI twin anchor it unambiguously against siblings like list_service_instances, get_service_package, and prepare_service_setup.

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 routes the agent: use this to enumerate packages, then pass a package_version_id to get_service_package for parameters and modes, or to prepare_service_setup to actually set one up. This gives both the when-to-use and the concrete next-step alternatives with the condition that selects them, leaving nothing to inference.

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.