Skip to main content
Glama
Sign In
BitPull

BitPull

by SamuealPK
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

bitpull_login

Starts a password-free login to BitPull by returning a link and code that the account owner must approve on the website. Check status afterwards to confirm the session is active.

Instructions

Log this computer in to BitPull without a password: returns a link and a code. SHOW THEM TO THE PERSON; only they can approve it on the website, where they are logged in. Never approve it yourself or ask for their password. The login completes in the background; check with bitpull_status or my_balance.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.6/5.0
Behavior5/5

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

With no annotations supplied, the description carries the full behavioral burden and does so: it discloses the return payload (link + code), the human-approval requirement, the prohibition on self-approval or password requests, and that login completes asynchronously in the background. This is exactly the auth and async semantics an agent needs before invoking.

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?

Three tight sentences, front-loaded with the action and its output, followed by the operating constraint and the verification path. The capitalized emphasis on showing the code to the person earns its space given the security stakes.

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?

No output schema exists, and the description compensates by describing what is returned and how completion is confirmed elsewhere. The only minor gap is that it does not say how long the link/code remains valid or what happens if approval never occurs.

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?

The tool takes zero parameters, so the baseline applies; the description adds the meaningful clarification that no password argument is required. Nothing further is needed from the schema side, which is empty at 100% coverage.

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?

States a specific verb and resource ('Log this computer in to BitPull') plus the no-password constraint, and immediately names what the call yields (a link and a code). That is enough for an agent to distinguish it from bitpull_logout or bitpull_status without opening any schema.

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?

Gives clear context for when to use it (passwordless login) and explicitly routes the follow-up step to bitpull_status or my_balance. It does not enumerate a when-not-to-use case, but the 'only they can approve it' constraint effectively excludes agent-side approval.

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