Skip to main content
Glama

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault

No arguments

Capabilities

Features and capabilities supported by this server

CapabilityDetails
tools
{
  "listChanged": false
}
prompts
{
  "listChanged": false
}
resources
{
  "subscribe": false,
  "listChanged": false
}
experimental
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
analyze_pr

Detailed PR analysis with signals and checklist. Use analyze_pr for deep analysis, coach_pr for quick pass/fail.

Returns: tier (low_risk/medium_risk/high_risk), signals (positive/negative/neutral), checklist (P0/P1/P2 items), and recommended_action.

Use this before submitting a PR to a large open-source repo to check if your contribution strategy is sound. Combines repo profile data, anti-pattern matching, and success pattern analysis.

Args: title: PR title (e.g. "feat: add new search endpoint") repo: Target repo in org/name format (e.g. "encode/httpx") body: PR body/description text description: Extended description (optional) author: PR author username author_association: Author's association with repo (NONE/CONTRIBUTOR/COLLABORATOR/MEMBER/OWNER) labels: PR labels (e.g. ["bug", "documentation"]) star_count: Repository star count (0 = unknown) repo_merge_rate: Repository's external PR merge rate 0.0-1.0 (0 = unknown)

Returns: dict with keys: tier, signals, checklist, recommended_action, repo, title

Example: analyze_pr("fix: timeout in connection pool", "encode/httpx", "Fixes #123") → {"tier": "medium_risk", "signals": {...}, "checklist": [...], "recommended_action": "..."}

coach_pr

Agent PR Dojo: quick pass/fail gate. Use coach_pr for go/no-go decision, analyze_pr for detailed analysis.

Use this as a final gate before opening a PR. Returns pass=true if safe to submit, pass=false if there are blocking issues to fix first.

Combines repo profile analysis, anti-pattern matching, and maintainer policy checks into a single go/no-go decision.

Args: title: PR title repo: Target repo (org/name) body: PR body/description description: Extended description author: PR author username author_association: Author's association (NONE/CONTRIBUTOR/etc.) labels: PR labels star_count: Repo star count repo_merge_rate: External PR merge rate (0.0-1.0)

Returns: dict with pass (bool), tier, signals, checklist, recommended_action

triage_pr

Policy-aware PR screening.

Reads docs/policies/-.md and checks the PR against hard/soft rules.

返回: verdict: pass / needs_preflight / warn / reject policy_loaded: bool violations: list of {rule, severity, evidence} generic_checks: list (only when needs_preflight) recommended_action: str (always)

Example: triage_pr("docs: typo", "Ikalus1988/MisakaNet", "fix typo", "docs/faq.md | 3 ++-") → {verdict: "pass", policy_loaded: true, ...}

triage_pr("docs: add installation", "pallets/flask", ...)
→ {verdict: "needs_preflight", generic_checks: [...6 items...], ...}
get_repo_profile

Get repository profile with maintainer guidelines, AI policy, and merge rate.

Returns 17 agent_guidelines fields including ai_policy, maintainer_vibe, external_merge_rate, close_keywords, and more. Use this to understand a repo's contribution culture before submitting a PR.

Args: repo: Repository in org/name format (e.g. "encode/httpx")

Returns: dict with repo metadata and agent_guidelines, or error if not found

list_open_prsA

List all open PR case studies in the knowledge base.

Returns PRs with final_status=open, useful for tracking ongoing contributions and their current state.

Returns: list of {repo, pr_number, pr_url, folder} for each open PR

get_case_studyA

Get a specific PR case study with full details and rounds.

Returns the complete case study including frontmatter, body text, and round-by-round interaction history. Useful for learning from past PR experiences.

Args: repo: Repository in org/name format pr_number: PR number (integer)

Returns: dict with frontmatter, body, path, or error if not found

search_patternsA

Search anti-patterns and success-patterns by keyword.

Use this to find relevant patterns before submitting a PR. Anti-patterns show what NOT to do, success-patterns show what works.

Args: query: Search keyword (e.g. "duplicate PR", "missing tests", "out of scope", "breaking change") pattern_type: Filter type — "all" (default), "anti-pattern", or "success-pattern" limit: Max results to return (default 10)

Returns: list of dicts with keys: key, title, symptom, fix_action, source_pr, type, file

Example: search_patterns("duplicate PR") → finds anti-patterns about duplicate submissions search_patterns("timeout", "anti-pattern") → finds timeout-related failure patterns

schema_info

返回支持的 schema 版本和枚举值。

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/zsxh1990/pr-genius'

If you have feedback or need assistance with the MCP directory API, please join our Discord server