Skip to main content
Glama
Orchestra MCP Server

Orchestra MCP Server

Official
by orchestra-hq

Get Workspace Git Connection

get_workspace_git_connection
Read-only

Retrieve the workspace-level Git provider link for an Orchestra account—provider and org/instance—to verify onboarding or confirm Git-backed pipeline setup.

Instructions

The workspace-level Git connection: whether a Git provider (GitHub, GitLab, Azure DevOps, Bitbucket) is linked to the Orchestra account itself, which one, and the org or instance that identifies it. This is the account link used for Git-backed pipelines, not the Git credentials an integration task uses (e.g. a Python or dbt task's repository connection); see list_integration_connections for those. Call it during onboarding, and again after the user links Git to confirm it.

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": "get_workspace_git_connection"
  }
}

Input Schema

NameRequiredDescriptionDefault
account_idNoAct on this account rather than the one the credential resolves to. Omit it to use the credential's own account. An API key is issued to a single account, so it may only name that account; an OAuth token may name any account its grant covers.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv2026.11.18-0

TDQS

A4.4/5.0
Behavior4/5

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

readOnlyHint=true already covers the safety profile and an output schema covers the return shape, so the description's job is lighter and it delivers the key behavioral distinction: this is the read-only account-level link, not per-task credentials. It stops short of describing auth scoping rules (API key vs OAuth account eligibility), but that detail is already carried by the account_id schema description.

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 identification of the resource and its provider/org payload is front-loaded, and the exclusion of integration credentials follows immediately. The one weakness is density: the first sentence chains whether/which/org into a single long clause, and could have been split for faster scanning.

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?

For a single optional-parameter read tool with an output schema and readOnly annotations, nothing needed to call it correctly is missing: the description supplies the meaning of the resource, the disambiguation from a same-sounding sibling, and the invocation moments. Return-value details are appropriately left to the output schema.

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% and the single account_id parameter is fully documented, including the API-key vs OAuth scoping nuance. The description adds nothing about account_id, so the baseline 3 applies — the schema does all the semantic work.

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 resource (the workspace/account-level Git connection) and enumerates exactly what the returned information is: whether a provider is linked, which provider (GitHub, GitLab, Azure DevOps, Bitbucket), and the org or instance identifier. It also explicitly contrasts itself with task-level Git credentials, so an agent can separate it from get_integration_connection without opening any schema.

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?

It gives concrete when-to-call guidance: during onboarding, and again after the user links Git to confirm. It also names the sibling list_integration_connections and the condition that selects it — when what's needed is an integration task's repository connection rather than the account link.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools