Skip to main content
Glama
Sign In
HAOps MCP Server

HAOps MCP Server

by tbranzov
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

haops_git_get_remote_url

Retrieve the SSH remote URL, default branch, and ready-to-use setup commands for pushing to HAOps Git. Supports multi-repo projects with an optional repository name.

Instructions

Get SSH remote URL and setup instructions for pushing to HAOps Git. Returns the SSH URL, default branch, and copy-pasteable setup commands. Supports multi-repo projects via repositoryName.

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": {
      "projectSlug": "<projectSlug>"
    },
    "name": "haops_git_get_remote_url"
  }
}

Input Schema

NameRequiredDescriptionDefault
projectSlugYesThe project slug (URL identifier)
repositoryNameNoRepository name for multi-repo projects (default: first/main repo)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.8.0

TDQS

A4.2/5.0
Behavior4/5

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

With no annotations, the description carries the full burden. It discloses that it returns SSH URL, default branch, and setup commands, and supports multi-repo. It does not mention side effects or permissions, but for a read-only tool that's acceptable.

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 concise sentences: main purpose, return values, multi-repo note. No wasted words, front-loaded, and efficiently structured.

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?

Given no output schema and no annotations, the description covers the main purpose, returns, and parameter usage. It is adequate for a simple get tool, though it omits potential error conditions.

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%, so baseline is 3. The description adds minimal value: it reinforces multi-repo support but does not provide new parameter semantics 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 clearly states the tool gets SSH remote URL and setup instructions, distinguishing it from other git tools like haops_git_commit_diff or haops_git_list_files. The verb 'Get' and resource 'SSH remote URL and setup instructions' are specific.

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 implies usage when needing remote URL and setup commands, but does not explicitly exclude alternatives or mention when not to use. It provides clear context but lacks explicit when-not or sibling comparisons.

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