Skip to main content
Glama
Sign In
BitPull

BitPull

by SamuealPK
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

bitpull_logout

Destructive

Log this computer out of its BitPull account before switching accounts. Lending stops until someone logs in again.

Instructions

Log this computer out of its BitPull account, e.g. before logging in with another account (then use bitpull_login). Only when the person asks. Lending on this computer stops until someone logs in again. Welcome credits are given once per computer, not again after switching accounts.

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": "bitpull_logout"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.6/5.0
Behavior4/5

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

Annotations only declare destructiveHint=true; the description goes beyond that by stating the concrete consequences — lending on this machine stops until re-login, and welcome credits are not re-granted after an account switch. It does not say anything about what local session state is cleared or whether work in progress is affected, which keeps it short of a 5.

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?

Four short sentences, front-loaded with the action and followed by the consequence and the consent rule. Every sentence carries information, though the credits note is tangential to the act of logging out.

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?

A parameterless, no-output-schema tool whose risks are fully covered: what it does, when to use it, what it disables, and the one irreversible side effect (credits). Nothing an agent needs before calling it is missing.

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?

Zero parameters, so there is nothing for the description to disambiguate; baseline applies. The description correctly spends no space on parameter talk.

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?

"Log this computer out of its BitPull account" is a specific verb plus resource plus scope (this computer, not the account globally). It is trivially distinguishable from bitpull_login, which it names directly.

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

Usage Guidelines5/5

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

Gives an explicit trigger ("before logging in with another account"), routes to the alternative (bitpull_login), and adds a consent gate ("Only when the person asks"). That is when-to-use, when-to-not-act-without-asking, and the alternative all in one.

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