Skip to main content
Glama
Sign In
BitPull

BitPull

by SamuealPK
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

bitpull_connect_account_page

Open the provider's page to create a BitPull key with the correct permission preselected, then paste the key into the app; never request or enter the key yourself.

Instructions

Open the provider's page where the person creates a key for BitPull (Cloudflare opens with the right permission already chosen). The person then pastes the key in the app: never ask for it or type it yourself.

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

Input Schema

NameRequiredDescriptionDefault
providerYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.7/5.0
Behavior4/5

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

Annotations only declare destructiveHint=false, so the description carries most of the burden and does add real context: it discloses the Cloudflare special case (correct permission pre-selected) and a security constraint that the agent must never request or type the key itself. It stops short of saying whether a URL is returned or a browser is launched.

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?

Two short sentences with no filler, and the action is front-loaded. The phrase 'the app' is slightly loose but does not impede understanding.

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

Completeness3/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 definition covers intent and the key-security rule, but leaves the return behavior (URL versus opened window) and the required follow-up step underspecified.

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?

Only one parameter, and the schema already enumerates the five providers. The description goes beyond the enum by explaining provider-specific behavior (Cloudflare preselects the right permission), which is meaningful added value.

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?

States a concrete action and resource: opening the provider's key-creation page for BitPull. It is clear what happens, though it doesn't explicitly distinguish itself from bitpull_open_account_page or bitpull_connect_tool by name.

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?

Usage is implied by the flow: hand off to the provider page so the person creates their own key. There is no explicit statement of when to prefer this over sibling tools like bitpull_connect_tool or bitpull_open_account_page, so the agent must infer the ordering.

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