Skip to main content
Glama
nixkeeper-mcp
by nixkeeper

Open nixpkgs issues

issues
Read-only

Search nixpkgs open reports by title to check Hydra build failures and update requests, including current build status, version availability, and update-bot plans.

Instructions

Search nixpkgs' open issues by title (the PR digest, hourly). Build-failure issues have hydra: what Hydra builds now say (builds: a candidate to close; failing; waiting; removed; ...); update requests have update: whether nixpkgs has the version asked (done, partly, open) and the update bot's plans.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "issues"
  }
}

Input Schema

NameRequiredDescriptionDefault
kindNobuild (build failures) or update (update requests).
limitNoAt most this many results (default 30).
searchNoPart of the title.
packageNoIssues about it: the package a build failure or update request names, or its name whole in the title (not pkg-config for pkg).
verdictNoThe digest's verdict: builds, failing, waiting, variant, noJob, platformNotBuilt, removed, renamed, unfree, markedBroken, notForHydra (build); done, partly, open, notFound, notVersion (update).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.4.1
    • changedInput schema / properties / package / description
      Previous value: -"Issues about it: the package a build failure or update request names, or every word of its name in the title."New value: +"Issues about it: the package a build failure or update request names, or its name whole in the title (not pkg-config for pkg)."
  2. First observedv0.3.0

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already cover the read-only/open-world safety profile, and the description adds genuinely new behavioral context: this is a derived hourly PR-digest view, and each issue kind carries different derived fields (hydra verdicts vs. update status). That provenance is useful and non-obvious, though the phrasing 'the PR digest, hourly' is terse.

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

Conciseness3/5

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

Purpose is front-loaded in the first clause, which is good, but the remainder is a single dense sentence with parenthetical chains ('builds: a candidate to close; failing; waiting; removed; ...') that is harder to parse than it needs to be.

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?

With no output schema and all five parameters documented in the schema, the description supplies enough context about data provenance and field semantics for correct invocation; missing only explicit sibling routing.

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 100%, so the baseline is 3, but the description goes further by explaining what verdict values mean in context ('builds: a candidate to close', 'whether nixpkgs has the version asked'), adding semantic meaning beyond the flat enum list.

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 ('Search nixpkgs' open issues by title') and immediately scopes it by the two issue kinds the tool covers. It does not name the nearest siblings (build_failures, update_attempts) to say how it differs from them, which keeps it below a 5.

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 implied by the descriptions of the two kinds and their fields, but there is no explicit when-to-use or when-to-prefer-a-sibling guidance despite overlapping siblings like build_failures and update_attempts being present.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.