Skip to main content
Glama

Get pipeline workspace profiles

get_pipeline_workspace_profiles
Read-only

List the workspace profile kinds a connected pipeline repository defines: the names an Ankra Workspace of that repository can be brought up as. Only the kinds are answered, never a profile's images or environment. Read-only; needs workspaces.use or workspaces.manage.

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": {
      "repository_id": "<repository_id>"
    },
    "name": "get_pipeline_workspace_profiles"
  }
}

Input Schema

NameRequiredDescriptionDefault
repository_idYesThe connected repository's id, from list_pipeline_repositories.

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?

Annotations already declare readOnlyHint=true, making the 'Read-only' sentence redundant, but the description adds genuine context the annotations lack: the required authorization scope (workspaces.use or workspaces.manage) and, importantly, the negative behavioral contract that profile images and environment are never returned. That negative guarantee is the most useful disclosure for an agent deciding whether this answers its question.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three short sentences, front-loaded with the verb and resource, then the semantic gloss, then the boundary condition and auth requirement. No filler and no repetition beyond the single 'Read-only' overlap with annotations.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

This is a simple one-parameter read tool with no output schema, and the description compensates by describing the shape of the answer (kinds only, no images or environment) and the permission needed. Nothing an agent requires to call it correctly is missing.

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?

There is a single parameter at 100% schema coverage, and the schema already explains that repository_id comes from list_pipeline_repositories. The description adds no further meaning about the id format or failure behavior, so the baseline of 3 for high-coverage schemas 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 — 'List the workspace profile kinds a connected pipeline repository defines' — and glosses the concept in domain terms ('the names an Ankra Workspace of that repository can be brought up as'). The negative scope clause ('Only the kinds are answered, never a profile's images or environment') further separates it from repository/profile-detail siblings.

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?

The description establishes the applicable context (a connected pipeline repository) and points at the parameter's source, list_pipeline_repositories, so an agent knows how to get here. It does not name an explicit alternative or a when-not case, so it stops short of full when/when-not guidance.

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.