Skip to main content
Glama
Sign In
BitPull

BitPull

by SamuealPK
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

bitpull_remove_model_folder

Remove a saved group model folder by providing its absolute path, so BitPull stops storing group models in that location.

Instructions

Stop saving group models in a folder.

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": {
      "path": "<path>"
    },
    "name": "bitpull_remove_model_folder"
  }
}

Input Schema

NameRequiredDescriptionDefault
pathYesAbsolute path of the folder

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.5/5.0
Behavior2/5

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

Annotations only declare destructiveHint=false, which is a low bar. The description does not clarify whether the folder or model files are affected, whether removal is reversible, or whether the models can be re-added. The phrase "Stop saving group models in a folder" is ambiguous about the actual side effects.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

It is a single short sentence with no waste, which is good, but it is terse to the point of ambiguity. Brevity here costs clarity rather than serving it.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a mutation-style tool with only one annotation and no output schema, the description needs to explain the effect and its relationship to siblings. It does not say what changes, what constraints the path has, or what happens on success.

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% with a single documented parameter, so the baseline is 3. The description adds no meaning about what the path refers to (a model folder versus any folder), leaving the schema's "Absolute path of the folder" as the only definition.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific action ("Stop saving") on a resource ("group models in a folder"). It is clearer than the name alone, but it does not distinguish this from bitpull_remove_folder or bitpull_add_model_folder, which look adjacent. An agent must infer the difference from names alone.

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

Usage Guidelines2/5

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

No when-to-use guidance, no prerequisites, and no mention of alternatives such as bitpull_remove_folder. The agent is left to guess whether this removes a folder from a model's saved set or deletes a folder outright.

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