Skip to main content
Glama
The-40-Thieves

codecalc

by The-40-Thieves
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Install Package

install_package
Destructive

Install a software package for a chosen language via its package manager (uv pip, npm, gem, go get, cargo add), requiring confirmation before installation.

Instructions

Install a package for a language (uv pip / npm / gem / go get / cargo add...).

Asks the caller to confirm before installing (a protocol-level gate, not just the anthropic/requiresUserInteraction _meta hint — see codecalc/confirmation.py); a declined or malformed confirmation refuses with no install attempted.

With session_id, executed code in that session can import the result.

NETWORK: yes, always. The package manager fetches from its registry (PyPI, npm, rubygems, crates.io). codecalc opens no socket itself; the child process does.

NOT SANDBOXED: the installer runs as a direct subprocess of the server, so install-time hooks (npm postinstall, Python build backends, Cargo build scripts) execute with the server user's filesystem access. The environment is still restricted to the allowlist, so secrets do not leak, but the filesystem is not confined. Do not point this at untrusted input. See SECURITY.md.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
packageYesPackage name to install via that language's manager (uv pip/npm/gem/go get/cargo add)
versionNoExact version to install; omit to install the manager's default/latest
languageYesLanguage whose package manager installs the package, e.g. 'python3', 'node'
session_idNoInstall into this session's workspace instead of the shared cache; omit for the shared cache

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changedv0.12.0
    • addedInput schema / properties / language / description
      Added value: +"Language whose package manager installs the package, e.g. 'python3', 'node'"
    • addedInput schema / properties / package / description
      Added value: +"Package name to install via that language's manager (uv pip/npm/gem/go get/cargo add)"
    • addedInput schema / properties / session_id / description
      Added value: +"Install into this session's workspace instead of the shared cache; omit for the shared cache"
    • addedInput schema / properties / version / description
      Added value: +"Exact version to install; omit to install the manager's default/latest"
  2. Changed1 schema field changedv0.11.0
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "additionalProperties": true,
+  "title": "install_packageDictOutput",
+  "type": "object"
+}
  3. Changed7 schema fields changedv0.2.0
    • removedInput schema / additionalProperties
      Removed value: -false
    • addedInput schema / properties / language / title
      Added value: +"Language"
    • addedInput schema / properties / package / title
      Added value: +"Package"
    • addedInput schema / properties / session_id / title
      Added value: +"Session Id"
    • addedInput schema / properties / version / title
      Added value: +"Version"
    • addedInput schema / title
      Added value: +"install_packageArguments"
    • changedOutput schema / (root)
      Previous value: -{
-  "additionalProperties": true,
-  "type": "object"
-}New value: +null
  4. First observedv0.1.0

TDQS

A4.5/5.0
Behavior5/5

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

The description goes beyond the destructiveHint annotation by explaining precisely why this is dangerous: it requires user confirmation, runs as a direct subprocess, triggers install-time hooks, and executes with the server user's filesystem access. It also flags network egress. This is exactly the kind of behavioral context a model agent needs before invoking a mutating tool.

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?

The description is compact, scannable, and every sentence adds value: the package-manager list clarifies scope, the confirmation note sets expectations, and the sandbox warning is essential. No filler or redundant restatement of the schema is present.

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?

For a destructive, network-touching installation tool, the description covers the critical operational context: languages supported, session behavior, confirmation requirement, network use, and lack of sandboxing. Given the schema already documents parameters and there is an output schema, nothing important is left for the agent to infer.

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 already 100%, with each parameter described in the input schema. The description adds useful examples for `language`, but the core parameter meanings remain in the schema. It does not materially clarify `package`, `version`, or `session_id` beyond what the schema already states.

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?

Description opens with a precise verb-object statement: 'Install a package for a language' and enumerates concrete package managers (uv pip, npm, gem, go get, cargo add). This makes the tool's role immediately unambiguous, even in a large sibling list.

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?

The description clearly frames when to use the tool—when a dependency needs to be installed into a language environment, with optional session scoping. It does not name a specific alternative to prefer over, but the package-manager examples make the intended context concrete. The security warning 'Do not point this at untrusted input' is a meaningful usage guardrail.

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