Skip to main content
Glama

Link GitHub repo

github_link_repo
Idempotent

Link a GitHub repo (owner/name) to the project

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

Input Schema

NameRequiredDescriptionDefault
repoYesowner/repo
branchNo
project_idNoProject id (or use session from use_project)
base_branchNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.8/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=false, idempotentHint=true, openWorldHint=true, and destructiveHint=false, so the safety profile is covered structurally. The description adds nothing beyond that — it does not say whether linking triggers a clone/sync, what happens on repeat linking, or how external GitHub access is authorized.

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?

A single front-loaded sentence with no filler; the action and its arguments come first. Its brevity is efficient, though it borders on under-specification rather than crispness.

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

Completeness3/5

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

For a simple 4-parameter mutation with annotations covering the safety profile and no output schema, the description is just barely sufficient to know the action. It leaves the two branch parameters and the post-link behavior unexplained, which matters for an open-world tool that reaches an external service.

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

Parameters2/5

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

Schema coverage is only 50%: repo and project_id are described in the schema, but branch and base_branch have no description anywhere. The description's "(owner/name)" merely restates the schema's own "owner/repo" hint and gives no meaning for the branch parameters or which default applies.

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

Purpose4/5

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

"Link a GitHub repo (owner/name) to the project" gives a specific verb (Link) and resource (GitHub repo) plus the target (project), so the core action is unambiguous. It does not distinguish this from neighboring tools such as github_sync, github_status, or github_pull, which an agent must disambiguate by name alone.

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?

There is no guidance on when to link versus sync or check PR/status, no prerequisites (GitHub auth, permissions, existing project), and no mention of what happens if the repo is already linked. The agent is left to infer all usage context from the name.

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.

Resources