Skip to main content
Glama

GitPicker

get_repo

获取一个 GitHub 仓库的元信息(描述、Stars、Forks、License、默认分支、Topics、主页)。当用户询问某个仓库的概况时使用。

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

Input Schema

NameRequiredDescriptionDefault
repoYes仓库名,如 next.js
ownerYes仓库属主,如 vercel

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full behavioral burden. It does disclose the response contents by enumerating the metadata fields, and 获取 implies a read-only operation, but it says nothing about authentication needs, rate limits, or failure behavior (e.g., what happens for a nonexistent owner/repo).

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: the first front-loads the action and the returned fields, the second gives the trigger condition. No redundant or filler text.

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 simple two-parameter read tool with fully documented params and an explicit field list (no output schema needed), the definition is nearly sufficient. The only gaps are operational details like auth, rate limiting, and error cases for invalid repositories.

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 coverage is 100%: both owner and repo are documented with concrete examples (vercel / next.js). The description adds no additional parameter meaning such as case sensitivity, slashes, or org-vs-user distinctions, so the baseline 3 is appropriate.

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?

States a specific verb (获取) and resource (GitHub 仓库元信息) and enumerates the exact fields returned (描述、Stars、Forks、License、默认分支、Topics、主页), which clearly separates it from siblings like get_issues, list_branches, or read_file. It stops short of naming any sibling to contrast against, so it lands just below the top score.

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?

"当用户询问某个仓库的概况时使用" gives a clear trigger condition that maps naturally onto the 'overview/metadata' intent. There are no exclusions or named alternatives (e.g., when to prefer search_repos to find a repo first), so routing is clear but not exhaustive.

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