Skip to main content
Glama

Create GitHub Repository

varity_create_repo

Create a new GitHub repository and push your local project code to it, giving you a repo URL to deploy from when no remote repository exists yet.

Instructions

Create a new GitHub repository and push your local project to it. Pass the 'path' parameter with the local project directory. This creates an empty repo and pushes your actual code to GitHub. varity_deploy builds from a Git repository URL (or takes a prebuilt image), so call this before varity_deploy when you have code locally but no repository yet. Requires GitHub CLI authentication or a GITHUB_TOKEN/GH_TOKEN environment variable with repository access.

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

Input Schema

NameRequiredDescriptionDefault
nameYesRepository name (lowercase, hyphens allowed, e.g. 'my-app')
pathNoAbsolute path to the local project directory to push to GitHub (e.g. '/home/user/my-app'). Pushes the actual project code. Pass its returned repo_url to varity_deploy.
visibilityNoRepository visibilityprivate
descriptionNoShort description of your app (optional)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv2.0.0
    • removedInput schema / properties / github_token
      Removed value: -{
      -  "description": "GitHub personal access token (optional if GITHUB_TOKEN env var is set). Needs 'repo' scope.",
      -  "type": "string"
      -}
    • changedInput schema / properties / path / description
      Previous value: -"Absolute path to the local project directory to push to GitHub (e.g. '/home/user/my-app'). When provided, pushes the actual project code. Required for custom apps that will use varity_deploy with dynamic hosting. If omitted, creates a repo from the Varity SaaS template instead."New value: +"Absolute path to the local project directory to push to GitHub (e.g. '/home/user/my-app'). Pushes the actual project code. Pass its returned repo_url to varity_deploy."
    • changedInput schema / properties / visibility / default
      Previous value: -"public"New value: +"private"
  2. First observedv2.0.0-beta.24

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare openWorldHint=true, idempotentHint=false, and destructiveHint=false; the description adds the important non-obvious behaviors: an empty repo is created and the local code is actually pushed, and authentication is required via CLI or token. It does not say what happens when a repo of the same name already exists or whether a partial failure leaves a dangling repo, which are the remaining gaps for a non-idempotent, open-world write.

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?

Front-loaded with the action and scope, then the prerequisite, then the sibling relationship, then auth — a sensible order. The 'push your code' concept is restated three times ('push your local project', 'pushes your actual code', 'Pushes the actual project code' in the path schema), so a sentence could be trimmed.

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?

Covers purpose, ordering versus the deploy sibling, auth prerequisites, and hints at the returned repo_url despite there being no output schema. Missing only edge-case behavior (name collision, failure/cleanup semantics) for a tool that performs an open-world, non-idempotent write.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3, but the description adds workflow meaning the schema lacks: 'path' causes the actual project code to be pushed, and its returned repo_url is the input to varity_deploy — information not derivable from the schema since there is no output 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?

States a specific verb and resource ('Create a new GitHub repository and push your local project to it') and immediately clarifies the two-step behavior (empty repo creation plus code push). It also distinguishes itself from the nearest sibling by naming 'varity_deploy' and explaining the relationship.

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?

Gives an explicit ordering rule: call this before varity_deploy when you have code locally but no repository yet. It also states the precondition (GitHub CLI auth or GITHUB_TOKEN/GH_TOKEN with repository access), so the agent knows when the tool is applicable and when it would fail.

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