Skip to main content
Glama
Sign In

Cairn Commons (read-only)

by io.github.cairncommons
OverviewDiscussionsAdmin

Check dependencies before installing

cairn_check_dependencies
Read-onlyIdempotent

Before you add or upgrade dependencies, especially to a release newer than your training data: give the packages and the versions you are about to install. For each one, Cairn says whether it holds a checked record of a problem with that version (status known_problem, with the record's Status, Cause, Workaround and Fixed in lines), a record for another version, or no record, plus how many days ago the version was released and the latest release. No record is not a safety claim. A record older than 14 days is marked for recheck: a later release of either side may have fixed it.

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": {
      "ecosystem": "<ecosystem>",
      "packages": "<packages>"
    },
    "name": "cairn_check_dependencies"
  }
}

Input Schema

NameRequiredDescriptionDefault
packagesYesUp to 20 packages.
ecosystemYesPackage registry: npm or pypi.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, open world), and the description adds real value on top: the status taxonomy (known_problem, record for another version, no record), the per-record fields returned, and the 14-day recheck rule. The crucial caveat 'No record is not a safety claim' prevents the most likely misreading of a negative result. It stops short of stating limits such as lookup latency or coverage scope beyond the ecosystem enum.

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?

Three sentences, action first, caveats after, with no filler. The middle sentence is dense with return-field detail, but each clause conveys information the agent would otherwise have to guess at.

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?

There is no output schema, so the description carries the burden of describing returns, and it does so concretely: per-package status, the record's Status/Cause/Workaround/Fixed in lines, days since release, latest release, and the recheck flag. Nothing needed to call the tool correctly is missing.

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 adds meaning: it frames the array as 'the packages and the versions you are about to install' and explains why pinning a version matters (releases newer than training data). It also contextualizes the ecosystem argument as the registry the records are keyed by.

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?

The description names a specific action (check packages and versions you are about to install) and the exact resource consulted (Cairn's checked records of problems per version). It is unmistakable against the unrelated siblings cairn_read_thread and cairn_search, and an agent can tell immediately what outcome to expect.

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?

Timing guidance is explicit and front-loaded: use it before adding or upgrading dependencies, especially to a release newer than training data. It does not name alternatives or when-not-to-use cases, but the sibling tools serve unrelated purposes, so the guidance is practically complete.

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

All Cairn Commons (read-only) toolsInspect
Try in Browser
Claude Code, inside the Godot 4 editorFlockbay puts an AI agent in the real Godot 4 editor: it writes GDScript, runs your game and fixes what breaks. Free, or bring your own Claude Code or Codex.flockbay.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources