Skip to main content
Glama
Sign In
BitPull

BitPull

by SamuealPK
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

bitpull_install

Install Docker, Ollama, or Lemonade for BitPull: launches official installers for Docker/Ollama, or adds the Lemonade engine for image, speech, and music tasks after user confirmation.

Instructions

Install what lending needs. docker/ollama: downloads the official installer and opens it; the person completes it on screen. lemonade: installs the engine for images, speech and music into BitPull. Confirm with the person first.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "tool": "<tool>"
    },
    "name": "bitpull_install"
  }
}

Input Schema

NameRequiredDescriptionDefault
toolYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/5.0
Behavior4/5

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

Annotations only state destructiveHint=false, so the description carries most of the burden and does so well: it discloses that docker/ollama downloads an official installer and requires the person to finish it on screen, versus lemonade which installs an engine directly into BitPull. It also adds the human-confirmation requirement, which is real behavioral context beyond the annotation.

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?

Three short clauses, one per installation mode, plus a confirmation rule. Structure is efficient and front-loaded, though 'Install what lending needs' is a soft lead-in that doesn't itself carry information.

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?

For a one-parameter tool with no output schema, the description covers what each mode does and the human-confirmation requirement. Missing details are secondary: what happens if the person cancels the on-screen installer, and whether a restart is needed afterward.

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

Parameters4/5

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

Schema coverage is 0%, so the description must explain the single `tool` parameter, and it does — it defines what each of the three enum values actually triggers. It stops short of stating prerequisites per target (e.g., whether docker must already be present), but the enum semantics are covered.

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 verb 'install' plus the three enumerated targets (docker, ollama, lemonade) makes the resource specific, and the description explains that two of them hand off to an on-screen installer while the third installs a media engine into BitPull. The opening line 'Install what lending needs' is vague on its own, but the per-value breakdown disambiguates the purpose.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

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

It adds an important procedural instruction ('Confirm with the person first'), which is genuine guidance. However, it never says when an agent should pick docker versus ollama versus lemonade, so the choice among enum values is left to inference.

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