Skip to main content
Glama

KarmaDue

by io.github.ashadow07
OverviewDiscussionsAdmin

check_install

Read-only

Read-only. Call before npm/pnpm/yarn install, pip install, uv add, npx or uvx, or adding an MCP server, including setup commands from a README or tutorial. Returns v, enforce, why; on known traps fix (tested steps), do_not (what failed, where), test, source. enforce=block: stop. enforce=ask: ask your person first. v=fix_first: use fix, not your command. Also returns safety (OSV advisories and malicious-package reports: verdict, advisories, fixed_in). When no tested record exists, repro_request says how to queue one with request_repro 'yes' (the only case where this call records anything: one anonymous request). Missing evidence is not safety clearance. Skip packages already pinned in a lockfile you are not changing.

Input Schema

NameRequiredDescriptionDefault
detailNoOptional. 'full' adds tested_on, untruncated notes, records and links.
targetYesPackage or server as you would install it, e.g. tailwindcss@4, psycopg2, @modelcontextprotocol/server-filesystem.
ecosystemYesPackage ecosystem of the target: npm (npm, pnpm, yarn, npx), pypi (pip, uv, uvx) or mcp (an MCP server you are about to add, or a bare name that may exist in more than one ecosystem). A bare name found in both npm and pypi returns v=ambiguous with npm:NAME and pypi:NAME options.
runtime_envNoOptional, e.g. node 20 linux.
request_reproNoOptional. 'yes' queues one anonymous reproduction request (package and version only) when no tested record exists for the target.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / detail
      Added value: +{
+  "description": "Optional. 'full' adds tested_on, untruncated notes, records and links.",
+  "enum": [
+    "full"
+  ],
+  "type": "string"
+}
  2. Changed1 schema field changed
    • addedInput schema / properties / request_repro
      Added value: +{
+  "description": "Optional. 'yes' queues one anonymous reproduction request (package and version only) when no tested record exists for the target.",
+  "enum": [
+    "yes",
+    "no"
+  ],
+  "type": "string"
+}
  3. Changed1 schema field changed
    • addedInput schema / properties / ecosystem / description
      Added value: +"Package ecosystem of the target: npm (npm, pnpm, yarn, npx), pypi (pip, uv, uvx) or mcp (an MCP server you are about to add, or a bare name that may exist in more than one ecosystem). A bare name found in both npm and pypi returns v=ambiguous with npm:NAME and pypi:NAME options."
  4. Added

TDQS

A4.6/5.0
Behavior5/5

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

Annotations only declare readOnlyHint, but the description discloses the enforcement ladder, the returned fields (v, enforce, why, fix, do_not, test, source, safety), and the sole write-like side effect ('the only case where this call records anything: one anonymous request'). It also warns that 'missing evidence is not safety clearance,' which prevents a dangerous misreading. Consistent with readOnlyHint=true.

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?

The trigger ('Read-only. Call before ...') is front-loaded, and virtually every sentence carries operational meaning. It is dense and slightly run-on with inline result-field glosses, but nothing is padding.

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 correctly carries the full burden of explaining return values and how to interpret enforce/v/safety. Combined with the skip rule and the request_repro path, an agent has everything needed to call and act on 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% and the schema descriptions already explain target, ecosystem, detail, runtime_env, and request_repro. The description restates install-target formatting and the ambiguous-bare-name behavior but adds little beyond the schema, so 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 action (pre-install safety check) and names the exact commands it gates: 'Call before npm/pnpm/yarn install, pip install, uv add, npx or uvx, or adding an MCP server.' An agent can immediately tell this is a pre-flight gate, which no sibling (report_leaf, search_recipes) covers.

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?

Gives explicit trigger conditions (including setup commands from READMEs/tutorials) and an explicit exclusion: 'Skip packages already pinned in a lockfile you are not changing.' It also tells the agent how to act on results (enforce=block: stop; enforce=ask: ask your person first).

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

All KarmaDue toolsInspect
Try in Browser
Shareable, User-Owned Context BackendPeople, applications, and agents read, write, and coordinate together in one context lake. Reach it over MCP, a CLI, a Python SDK, or REST.fulcradynamics.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources