Skip to main content
Glama

Register a GitHub repository as a source

add_github_source
Idempotent

Fetch a GitHub repository, index its skills and agents, and register it as a searchable registry source so its entries can be discovered.

Instructions

Fetch a GitHub repository, index its skills and agents, and register it as a registry source so its entries become searchable. Not covered by install_skill_from_github, which installs a single skill into a harness.

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

Input Schema

NameRequiredDescriptionDefault
refNoBranch, tag or commit to fetch.
repoYesowner/repo, owner/repo@ref, or a github.com URL.
applyNoWhen false, the fetch is described but nothing is written.
labelNoDisplay name for the source.
timeout_msNoHow long the fetch may take, in milliseconds.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, idempotentHint=true, destructiveHint=false and openWorldHint=true, so the safety profile is covered. The description adds that indexing happens and entries become searchable, but says nothing about authentication against GitHub, rate limits, or what happens when the same source is registered twice (left to idempotentHint).

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?

Two sentences, zero filler, with the core action and the sibling exclusion front-loaded before any caveat. Nothing is repeated from the title or schema.

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?

For a mutating, open-world registration tool with no output schema, the description covers what is written and why, and annotations carry reversibility and idempotency. It is slightly thin on external prerequisites (GitHub auth, fetch duration expectations) given the openWorldHint.

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 all five parameters are already documented in the schema, including the repo formats and the apply dry-run flag. The description adds no parameter-level meaning, so the baseline 3 applies.

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 chain and resource: fetches a GitHub repo, indexes its skills and agents, registers it as a registry source, and names the resulting benefit (entries become searchable). It also explicitly excludes install_skill_from_github, so an agent can separate the two without opening schemas.

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 second sentence gives a clear negative boundary against the closest sibling (single-skill install into a harness), which is the main confusion risk. It does not give positive guidance on when to prefer this over list_sources or search_registry, but the purpose statement implies the registration workflow.

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