Skip to main content
Glama

Get service package

get_service_package
Read-only

Read one managed-service package version (the twin of ankra services packages get): its contract - the operating modes it supports, its parameters with their defaults and bounds, and the secret inputs it takes. 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": {
      "package_version_id": "<package_version_id>"
    },
    "name": "get_service_package"
  }
}

Input Schema

NameRequiredDescriptionDefault
package_version_idYesPackage version id (UUID) from list_service_packages.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, making the trailing 'Read-only.' largely redundant, but the description adds real value by disclosing the shape of the returned contract: operating modes, parameter defaults and bounds, and secret inputs. This is meaningful disclosure for a tool with no output schema.

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?

One front-loaded sentence with the identifying clause first. The parenthetical CLI parity note ('the twin of `ankra services packages get`') is the only expendable element for an agent audience.

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 one parameter, full schema coverage, and no output schema, the description supplies the missing piece: what the returned contract consists of. Nothing an agent needs in order to call it correctly is absent.

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% and the single parameter's description already says it is a UUID from list_service_packages. The description adds no further meaning about the id beyond what the schema provides, so the baseline of 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('Read one managed-service package version') and enumerates what the resource contains (modes, parameters, secret inputs), so the agent knows it is a single-item fetch. It does not name the sibling list_service_packages explicitly, though the schema's id reference implies the pairing.

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?

Usage is only implied: an agent infers it should call this after obtaining an id from list_service_packages, which the schema states. There is no explicit when-to-use/when-not or alternative named in the description itself.

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.