Skip to main content
Glama
RogueAlg0

taken

by RogueAlg0
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

check_issue

Check if a GitHub issue is already taken before volunteering. Returns GO, TAKEN, or CAUTION by scanning linked PRs, assignees, and claimant comments.

Instructions

Check whether a GitHub issue is already taken.

Verdicts: GO (free to volunteer), TAKEN (spoken for: closed, open PR, or assignee), CAUTION (soft signal: someone expressed interest, the repo bans AI contributions, or the repo looks stale).

The payload also carries friendly_labels (first-time-contributor labels on the issue) and welcoming (repo-level signs contributions are welcome), the same markers scan_repo returns.

Error payloads carry error plus error_code: RateLimitError -> rate_limited, NotFoundError -> not_found, HTTP 401/CLI authentication failures -> auth_failed, subprocess timeouts -> timeout, other TakenError failures -> unknown.

Args: owner: repository owner login repo: repository name issue_number: issue number to check me: your GitHub login; your own comments are ignored in the claimant scan graphql: force the GraphQL fetch path instead of the automatic choice persistent_session: force the persistent-session GraphQL path instead of the automatic one pr_idle_days: stale-claim decay threshold for idle linked PRs (default 90) claim_silence_days: stale-claim decay threshold for simple issues (default 7) claim_silence_complex_days: stale-claim decay threshold for complex issues (default 14)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
meNo
repoYes
ownerYes
graphqlNoForce the GraphQL path. Default: automatic from auth state.
issue_numberYes
pr_idle_daysNoStale-claim decay: days of linked-PR inactivity before TAKEN weakens to CAUTION. Default: 90.
claim_silence_daysNoStale-claim decay: days one claim blocks as CAUTION on a simple issue; the clock resets on claimant activity. Default: 7.
persistent_sessionNoForce the persistent-session GraphQL path; token from `gh auth token` held in memory only. Default: automatic from auth state.
claim_silence_complex_daysNoStale-claim decay: days one claim blocks as CAUTION on a complex issue. Default: 14.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv0.9.2
    • addedInput schema / properties / claim_silence_complex_days
      Added value: +{
+  "anyOf": [
+    {
+      "minimum": 0,
+      "type": "integer"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "Stale-claim decay: days one claim blocks as CAUTION on a complex issue. Default: 14.",
+  "title": "Claim Silence Complex Days"
+}
    • addedInput schema / properties / claim_silence_days
      Added value: +{
+  "anyOf": [
+    {
+      "minimum": 0,
+      "type": "integer"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "Stale-claim decay: days one claim blocks as CAUTION on a simple issue; the clock resets on claimant activity. Default: 7.",
+  "title": "Claim Silence Days"
+}
    • addedInput schema / properties / pr_idle_days
      Added value: +{
+  "anyOf": [
+    {
+      "minimum": 0,
+      "type": "integer"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "Stale-claim decay: days of linked-PR inactivity before TAKEN weakens to CAUTION. Default: 90.",
+  "title": "Pr Idle Days"
+}
  2. Changed2 schema fields changedv0.7.3
    • changedInput schema / properties / graphql / description
      Previous value: -"Fetch via one GraphQL query (gh api graphql) instead of REST. Opt-in."New value: +"Force the GraphQL path. Default: automatic from auth state."
    • changedInput schema / properties / persistent_session / description
      Previous value: -"GraphQL over one persistent HTTPS connection; token from `gh auth token` held in memory only. Opt-in."New value: +"Force the persistent-session GraphQL path; token from `gh auth token` held in memory only. Default: automatic from auth state."
  3. Changed2 schema fields changedv0.7.2
    • addedInput schema / properties / graphql
      Added value: +{
+  "default": false,
+  "description": "Fetch via one GraphQL query (gh api graphql) instead of REST. Opt-in.",
+  "title": "Graphql",
+  "type": "boolean"
+}
    • addedInput schema / properties / persistent_session
      Added value: +{
+  "default": false,
+  "description": "GraphQL over one persistent HTTPS connection; token from `gh auth token` held in memory only. Opt-in.",
+  "title": "Persistent Session",
+  "type": "boolean"
+}
  4. First observedv0.5.0

TDQS

A4.1/5.0
Behavior4/5

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

With no annotations, the description carries the whole burden and does so well: it enumerates the decision thresholds, the stale-claim decay defaults, the two extra payload markers, and a full error-to-code mapping (rate_limited, not_found, auth_failed, timeout, unknown). It never explicitly states the operation is read-only/no-side-effect or names auth requirements beyond the `gh auth token` hint, which keeps it from a 5.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Purpose is front-loaded in one line, followed by logically grouped verdict, payload, error, and args sections; the error-code mapping is dense and useful rather than padding. Length is justified by the tool's complexity, though the arg list partially restates schema entries.

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 9-parameter tool with no output schema and no annotations, the description is notably complete: it describes the return verdict semantics, auxiliary payload fields, and error payload structure alongside every parameter. Missing pieces are rate-limit behavior and an explicit statement of read-only safety, which are minor gaps at this complexity.

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

Parameters4/5

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

Schema coverage is only 56%, so the description must compensate, and it largely does: it lists all nine args and adds genuine meaning for `me` ('your own comments are ignored') and for the three decay thresholds, which are otherwise opaque. The owner/repo/issue_number entries are trivial restatements, but the non-obvious parameters are explained.

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 ('Check whether a GitHub issue is already taken') plus a three-value verdict taxonomy (GO/TAKEN/CAUTION) that pins down exactly what the tool answers. The remark that it returns the same markers as `scan_repo` implicitly frames it as the per-issue counterpart to the repo-level sibling, so an agent can separate them.

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

Usage Guidelines3/5

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

Usage is only implied: a GO verdict maps naturally to 'free to volunteer', which hints at the pre-contribution workflow, but the description never states when to call this versus `scan_repo` or `discover_candidates`, nor any prerequisites or exclusions. The sibling names appear only as a reference for shared output markers, not as routing alternatives.

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