Skip to main content
Glama
Sign In
GitHub MCP Server

GitHub MCP Server

by BBsBrezz
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

github_get_repository

Retrieve detailed information about a specific GitHub repository by providing its owner/repo identifier. Use it to inspect repository metadata, settings, and key details.

Instructions

獲取特定倉庫的詳細資訊

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

Input Schema

NameRequiredDescriptionDefault
repositoryYes倉庫標識 (格式: owner/repo，例如: "octocat/Hello-World")

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.1/5.0
Behavior2/5

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

沒有任何 annotations，描述須獨自承擔行為揭露責任，但僅說「獲取詳細資訊」，未說明回傳哪些欄位、是否需要認證、是否會受速率限制或權限影響。雖然「獲取」隱含唯讀操作，但缺乏更進一步的行為資訊。

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?

單句極簡描述，動詞與資源前置，沒有任何冗餘字詞，對一個只有單一參數的簡單讀取工具而言恰到好處。

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?

工具複雜度低（單一參數、無巢狀物件、無輸出 schema），描述雖簡短但足以讓代理理解用途；惟「詳細資訊」究竟包含什麼內容完全未交代，且無 annotations 輔助，仍有明顯缺口。

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 描述覆蓋率為 100%，repository 參數已在 schema 中完整說明格式（owner/repo 及範例），描述未再補充任何參數層級資訊。依規則此情況基準即為 3 分。

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?

明確的動詞「獲取」加上資源「特定倉庫」，清楚指出這是取得單一倉庫的詳細資訊，與兄弟工具 github_get_repositories（列表）隱含區隔。但未明確點名任何兄弟工具作為對照，因此未達 5 分。

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?

完全沒有說明何時該用此工具、何時該改用 github_get_repositories 或 github_get_file_content 等替代工具，也沒有提及任何前置條件。使用時機只能靠工具名稱推斷。

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