Skip to main content
Glama
Sign In
BitPull

BitPull

by SamuealPK
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

bitpull_disconnect_account

Remove a connected hosting or database provider account from this computer by deleting its stored key. Already published sites remain online; use it to revoke local access for Cloudflare, Vercel, Supabase, Neon, or Upstash.

Instructions

Forget a connected hosting or database account on this computer (the key is deleted here; sites already published stay online).

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": {
      "provider": "<provider>"
    },
    "name": "bitpull_disconnect_account"
  }
}

Input Schema

NameRequiredDescriptionDefault
providerYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/5.0
Behavior3/5

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

Annotations only declare destructiveHint=false, and the description usefully explains that limited blast radius (only the local key is deleted; live sites are untouched), which is real added value. However, with essentially no other annotation coverage, it omits whether a confirmation is required, whether the call errors when no account is connected, and what the user must do to reconnect.

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?

One front-loaded sentence with the consequence in a tight parenthetical; no filler. The phrase 'Forget' plus the local-scope qualifier lands immediately.

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 local disconnect operation with no output schema, the description covers the essential surprise (remote sites stay online) and where the deletion happens. Remaining gaps — error behavior when not connected, reconnection path — are minor for this complexity level.

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 0% but the single parameter is a self-describing enum of five provider names, so the schema carries most of the meaning. The description only hints at the parameter's nature ('hosting or database account'), without mapping providers to categories or explaining invalid-provider behavior.

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?

Uses the specific verb 'Forget' against a concrete resource ('a connected hosting or database account') and scopes it with 'on this computer,' which separates it from remote-side siblings such as bitpull_publish_site or bitpull_claim_database. It never names a sibling explicitly, so it stops short of full differentiation.

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 parenthetical gives clear decision context: the credential is removed locally but published sites remain online, which is the key fact an agent needs before deciding to call it. It does not state exclusions or what happens when the provider is not connected, so it falls short of explicit when/when-not guidance.

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