Skip to main content
Glama
The-40-Thieves

codecalc

by The-40-Thieves
OverviewSchemaRelated ServersScoreDiscussions
Python
Local

install_package

Installs a package using its language's native manager (uv pip, npm, gem, go get, cargo add) into a session's workspace for import by executed code; without session_id, installs to the shared cache.

Instructions

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

With session_id, installs into that session's workspace so executed code can import it. Without, installs into a shared cache.

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
packageYes
versionNo
languageYes
session_idNo

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. 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
  2. First observedv0.1.0

TDQS

A4.1/5.0
Behavior5/5

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

There are no annotations, so the description carries the full burden of behavioral disclosure. It explicitly warns about network use, child-process registry access, install-time hooks, non-sandboxed filesystem access, allowlist restrictions, and untrusted input. This is unusually thorough and materially helps an agent understand the risks.

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 well structured and front-loaded: purpose, session behavior, network behavior, then security warning. Every sentence adds meaningful information, and the formatting uses caps labels and clear sections without waste or repetition.

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?

Given that there are no annotations and no output schema, the description is unusually complete for a network-touching, mutating tool. It covers workspace scoping, cache behavior, network, and security implications. The only remaining gaps are exact accepted language values, package/version syntax, and expected success/error return behavior.

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?

The schema provides no descriptions for any of the four parameters, so the description must compensate. It does explain the behavioral meaning of session_id and hints at supported language values through examples, but it does not clarify the expected format of package or version, leaving those to inference.

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?

The description clearly names a concrete action (install) and a concrete resource (a package for a language), with helpful package-manager examples. It does not explicitly distinguish itself from sibling tools such as execute_code, but the core purpose is unambiguous.

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 provides clear usage context: with a session_id it installs into that session workspace; without one it installs into the shared cache. It also notes that network access is always required, but it does not explain when to choose another tool instead or when installation should be avoided.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/The-40-Thieves/codecalc'

If you have feedback or need assistance with the MCP directory API, please join our Discord server