Skip to main content
Glama
Sign In
Uploadkit

Uploadkit

by drumst0ck
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

get_install_command

Get the correct shell command to install UploadKit packages based on your project's package manager. Supports pnpm, npm, yarn, and bun.

Instructions

Return the exact shell command to install UploadKit packages for a given package manager.

When to use: before asking the user to add dependencies — match their package manager (detect from the presence of pnpm-lock.yaml / package-lock.json / yarn.lock / bun.lockb if you can, otherwise ask or default to pnpm). Saves you from guessing pnpm vs npm vs yarn vs bun syntax.

Returns: a plain-text shell command as a single string (e.g. "pnpm add @uploadkitdev/react @uploadkitdev/next"). Read-only, idempotent, never modifies anything.

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_install_command"
  }
}

Input Schema

NameRequiredDescriptionDefault
packagesNoWhich UploadKit packages to install. Omit to get the default full-stack set: ["@uploadkitdev/react", "@uploadkitdev/next"]. Pass a subset to scope the command, e.g. ["@uploadkitdev/core"] for a framework-agnostic project, or ["@uploadkitdev/react"] for a React app without Next.js.
packageManagerNoWhich package manager's syntax to output. Default: "pnpm". Pick the one the user's project actually uses — check their lockfile.pnpm

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv0.1.1
    • addedInput schema / properties / packageManager / description
      Added value: +"Which package manager's syntax to output. Default: \"pnpm\". Pick the one the user's project actually uses — check their lockfile."
    • changedInput schema / properties / packages / description
      Previous value: -"Which UploadKit packages to install. Default: [\"@uploadkitdev/react\", \"@uploadkitdev/next\"]."New value: +"Which UploadKit packages to install. Omit to get the default full-stack set: [\"@uploadkitdev/react\", \"@uploadkitdev/next\"]. Pass a subset to scope the command, e.g. [\"@uploadkitdev/core\"] for a framework-agnostic project, or [\"@uploadkitdev/react\"] for a React app without Next.js."
  2. First observedv0.1.0

TDQS

A4.5/5.0
Behavior5/5

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

With no annotations provided, the description fully discloses the tool's safety profile: 'Read-only, idempotent, never modifies anything.' It also specifies the return format (a plain-text shell command as a single string), which is essential behavioral context beyond the schema.

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 concise and well-structured: each paragraph serves a distinct purpose (what it does, when to use, what it returns). It is front-loaded with the main verb and resource, and every sentence adds value without redundancy.

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?

The tool is simple (2 optional params, no output schema), and the description covers both the return value and the operational context. It explains when and how to use the parameters (e.g., detecting package manager from lockfile) and explicitly states the read-only behavior, making it complete for an agent to invoke correctly.

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 description coverage is 100% for both parameters, with detailed explanations, examples, and enums. The description itself adds little beyond the schema, only repeating the package manager concept and providing an example command. Baseline 3 is appropriate when the schema carries the parameter semantics.

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 states a specific verb ('Return') and resource ('exact shell command to install UploadKit packages'), clearly distinguishing it from siblings that fetch components or docs. It also includes a concrete example command, leaving no ambiguity about the tool's function.

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 explicitly says when to use the tool ('before asking the user to add dependencies') and even provides detection guidance for package managers. It does not explicitly mention when-not-to-use or alternatives, but given that sibling tools are unrelated, the context is clear enough.

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