Skip to main content
Glama
zsxh1990

pr-genius

by zsxh1990
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

list_open_prs

Read-onlyIdempotent

Find open PR case-study records—not live GitHub PRs—in the local knowledge base by repository or author for contribution strategy review.

Instructions

List open PR case-study records in the local knowledge base (issue #74).

NOTE: these are local case-study folders with final_status=open — NOT live GitHub PRs. For live GitHub PR health use status_prs.

Args: repo: filter by target repo (org/name, e.g. "encode/httpx"); "" = all author: filter by PR author username; "" = all

Returns: list of {repo, pr_number, pr_url, author, folder} for each matching open case study

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
repoNo
authorNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv2.1.4
    • addedInput schema / properties / author
      Added value: +{
+  "default": "",
+  "title": "Author",
+  "type": "string"
+}
    • addedInput schema / properties / repo
      Added value: +{
+  "default": "",
+  "title": "Repo",
+  "type": "string"
+}
  2. Addedv1.3.1

TDQS

A4.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint/idempotentHint/non-destructive, so the safety profile is covered. The description adds genuine context beyond that: it clarifies the records are local case-study folders with final_status=open rather than live data, and specifies the return fields. It does not cover pagination or ordering, so it falls just short of the top.

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?

Front-loaded with the core purpose, then a NOTE for the critical disambiguation, followed by scannable Args/Returns blocks. Every line earns its place with no filler.

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

Completeness5/5

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

No output schema exists, so the description correctly spells out the returned fields ({repo, pr_number, pr_url, author, folder}). Combined with annotations covering safety and full parameter documentation, an agent has everything needed to call this correctly.

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

Parameters5/5

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

Schema description coverage is 0%, so the description must carry the burden — and it does, documenting both params: `repo` filters by target repo with format example 'org/name' and '`""` = all', and `author` filters by PR author username with the same empty-string default semantics.

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 and resource ('List open PR case-study records in the local knowledge base') and immediately disambiguates the misleading name by clarifying these are NOT live GitHub PRs. An agent can tell it apart from status_prs without opening the schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly names the alternative for the other case: 'For live GitHub PR health use `status_prs`.' It gives a clear when-to-use boundary and an exclusion, leaving nothing to inference.

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