Skip to main content
Glama
Sign In

Carrick

by io.github.carrick-tools
OverviewDiscussionsAdmin

Read npm dependencies and version conflicts

get_service_dependencies
Read-onlyIdempotent

Read npm dependencies: one service's full package list, or org-wide conflicts when called without a service. Conflicts are graded on the semver ranges written in package.json, not on version strings: a package is listed only when no single install satisfies every service's range; error means the ranges span different majors, warning means they miss within one major. Each conflict carries a one-sentence summary naming the groups. Call it before adding or bumping a package.

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": "get_service_dependencies"
  }
}

Input Schema

NameRequiredDescriptionDefault
repoNoYour repo as owner/repo (git remote) or just the repo name. Resolves which Carrick project to query.
projectNoCarrick project slug to query. Omit to auto-resolve via `repo`, or omit both when the workspace has one project.
serviceNoService name (omit for org-wide conflict analysis)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / additionalProperties
      Added value: +false
  2. First observed

TDQS

A4.5/5.0
Behavior5/5

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

Annotations already cover read-only, idempotent, non-destructive, so the description is free to spend its words on genuinely non-obvious behavior: conflicts are graded on semver ranges in package.json rather than installed versions, only packages with no satisfying single install are listed, and error/warning map to different-majors vs. within-one-major gaps. That is substantive semantics no annotation conveys.

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?

Four tight sentences, front-loaded with the dual-mode statement, then the grading rule, then the trigger. Every sentence carries distinct information with no restatement of the title or annotations.

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, and the description compensates by explaining the return shape: what qualifies as a conflict, the two severity levels and their meanings, and the per-conflict `summary` field. Combined with full param coverage, an agent has everything needed to call and interpret it.

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

Parameters3/5

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

Schema coverage is 100%, so repo, project, and service are already documented, and the description's 'without a service' restates what the service param description already says. It adds no syntax or precedence detail for repo vs. project beyond the schema. Baseline 3 applies.

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 (read npm dependencies) and immediately disambiguates the two operating modes: one service's package list vs. org-wide conflict analysis when called without a service. An agent can tell what it will get 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 Guidelines4/5

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

Gives an explicit trigger: "Call it before adding or bumping a package." The omit-service condition is also spelled out as a mode selector. It does not name a sibling alternative (e.g., check_compatibility) or state when not to use it, so it falls short of a 5.

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

All Carrick 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