Skip to main content
Glama

Publish service package

publish_service_package
Destructive

Publish a managed-service package version to this organisation's catalogue from its contract document (the twin of ankra services packages publish), so the services one of the organisation's own stack profiles deploys can be set up from the catalogue and connected to applications. Build the document as schema_version 2: name (a DNS label), version (semantic version), publisher_id and profiles.customer from get_service_profile_pin, capability (one of logs, metrics, traces, database, cache, queue, search or object_storage), parameters, secrets and outputs (each an array, may be empty), lifecycle (verify, upgrade, recovery and delete set to stack-profile-verify, stack-profile-upgrade, stack-profile-recovery and stack-profile-delete), and connection: the wire protocol consumers speak (postgres, redis, nats, opensearch, s3, victorialogs or victoriametrics), the engine's Service and port in the instance namespace as endpoints[0] (name primary, with the protocol's URL scheme), the Secret holding its credentials as secret_name and secret_keys, and in fields where each of the protocol's connection fields comes from (kind secret_key with the key, literal with the value, or primary_host / primary_address with no value). Read the profile's manifests or a running instance (get_services, get_secrets) for the Service, port and Secret rather than guessing them. A refused document answers with the path that failed; fix that part and publish again. A published version cannot change: the same name and version with identical content returns it, different content is refused, so a change needs a new version. Publishing makes the package available to set up here; it does not make Ankra operate or qualify it. Requires profiles.write.

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": {
      "package": "<package>"
    },
    "name": "publish_service_package"
  }
}

Input Schema

NameRequiredDescriptionDefault
packageYesThe package contract document as a JSON object (schema_version 2), at most 256 KiB.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.3/5.0
Behavior4/5

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

Beyond the annotations it discloses prerequisites (requires profiles.write), partial-failure behaviour (a refused document answers with the path that failed), immutability semantics (identical content returns the existing version, differing content is refused, so changes need a new version), and scope limits (publishing does not make Ankra operate or qualify the package). One tension: the annotations set idempotentHint=false while the description describes same-name/same-version/identical-content returning the existing version, and destructiveHint=true is never explained (no guidance on removing or superseding a published version).

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?

Purpose is correctly front-loaded in sentence one, but the remaining ~300 words form a single dense paragraph mixing document schema, sourcing advice, and failure semantics with no grouping or formatting. Almost every clause carries information, yet the lack of structure makes the document contract hard to extract at a glance.

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 one-parameter tool whose parameter is a large nested object with only a one-line schema description and no output schema, the description carries the needed burden well: it specifies the document shape, where to source values, failure behaviour and immutability. It still leaves gaps on optional versus required document fields and on what an accepted publish returns to the caller.

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

Parameters5/5

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

The schema only says the single `package` parameter is a JSON object at schema_version 2 up to 256 KiB; the description supplies the actual document contract — required keys, the capability enum list, the protocol enum list, the endpoints[0]/secret_name/secret_keys layout, and the kind discriminator (secret_key, literal, primary_host, primary_address). That is far more meaning than the schema conveys, and the size limit is already handled by 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?

The first sentence gives a specific verb and resource (publish a managed-service package version into the organisation's catalogue from a contract document) and anchors it to the CLI twin `ankra services packages publish`. It also states the downstream effect (stack-profile-deployed services can be set up from the catalogue and connected to applications), which separates it from `list_service_packages`/`get_service_package` reads and from `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 Guidelines4/5

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

It gives concrete sourcing guidance: get publisher_id and profiles.customer from `get_service_profile_pin`, and read the Service, port and Secret from the profile's manifests or a running instance via `get_services`/`get_secrets` rather than guessing. It also says what to do on refusal (fix the failing path, publish again). What's missing is an explicit when-not-to-use clause (e.g. versus create_chart_service_profile or publish_stack_profile_draft), so it stops short of full alternative routing.

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.