Skip to main content
Glama
Sign In
github-mcp

github-mcp

by Eyalm321
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

github_migrations_unlock_repo_for_org

Unlock a repository in an organization after a migration by providing the organization, migration ID, and repository name.

Instructions

Unlock an organization repository

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": {
      "org": "<org>",
      "migration_id": "<migration_id>",
      "repo_name": "<repo_name>"
    },
    "name": "github_migrations_unlock_repo_for_org"
  }
}

Input Schema

NameRequiredDescriptionDefault
orgYesorg
migration_idYesmigration_id
repo_nameYesrepo_name

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.0.2

TDQS

C2.3/5.0
Behavior2/5

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

With no annotations, the description must disclose behavior, but it only states the action without explaining side effects, required permissions, or consequences. It does not mention that this is part of a migration workflow or that it reverses a previous lock.

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

Conciseness3/5

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

The description is very short (one sentence) but fails to convey essential information. Conciseness is not beneficial when it omits necessary context; the sentence does not earn its place as it merely repeats the tool name.

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

Completeness2/5

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

Given the complexity of GitHub migrations and the lack of an output schema or annotations, the description is incomplete. It does not explain the purpose of unlocking a repository, the relationship to migration_id, or what happens after unlocking.

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 baseline is 3. Although the parameter descriptions in the schema are minimal (just parameter names), the tool description adds no additional meaning to the parameters (org, migration_id, repo_name).

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose2/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description restates the tool name without adding specificity. It says 'Unlock an organization repository', which is essentially the same as the tool name. There is no differentiation from sibling tools or clarification of what 'unlock' means in the context of migrations.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No guidance is provided on when or why to use this tool versus alternatives. There is no context about the migration process or prerequisites for unlocking a repository.

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