Skip to main content
Glama

Get service profile pin

get_service_profile_pin
Read-only

Read the pin a managed-service package needs for one version of a stack profile this organisation owns (the lookup ankra services packages init makes): profile is the id, version_id and content digest the package's profiles.customer must carry, and organisation_id is the package's publisher_id. Use it before publish_service_package. Requires profiles.read. 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": {
      "profile_id": "<profile_id>",
      "profile_version_id": "<profile_version_id>"
    },
    "name": "get_service_profile_pin"
  }
}

Input Schema

NameRequiredDescriptionDefault
profile_idYesStack profile id (UUID) from list_stack_profiles.
profile_version_idYesId (UUID) of the profile version to pin, from get_stack_profile.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.1/5.0
Behavior4/5

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

Beyond the readOnlyHint annotation, the description adds the required `profiles.read` permission and explains the returned pin's fields, including profile id, version id, content digest, and publisher id. It does not cover failure modes, but the added auth and output semantics are meaningful for a read-only tool.

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?

The purpose is front-loaded and the description is not padded. The first sentence is dense with nested clauses, and 'Read-only' repeats the annotation, but the content is largely useful and appropriately sized.

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 tool with no output schema, the description supplies the key purpose, permission requirement, sequencing relative to publishing, and the returned pin fields. Minor gaps remain around error behavior and exact parameter-to-output mapping, but the definition is callable as written.

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 defines both required UUID parameters and their sources. The description adds context about the stack profile version and package pin but does not materially clarify the input parameters beyond 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 description states a specific verb and resource: reading the pin a managed-service package needs for one version of a stack profile. It distinguishes the purpose from broader profile tools by tying it to package publishing and the `ankra services packages init` lookup.

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 clear sequencing guidance with 'Use it before publish_service_package' and identifies the related CLI lookup. It does not explicitly name alternative tools or when not to use this one, but the context is clear enough for selection.

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.