Skip to main content
Glama
Sign In
BitPull

BitPull

by SamuealPK
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

bitpull_claim_database

Opens a link to claim a site folder's temporary Neon database into your own Neon account; each claim link expires after 15 minutes.

Instructions

Open a new link to claim the temporary Neon database of a site folder into the person's own Neon account (each link lasts 15 minutes).

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": {
      "folder": "<folder>"
    },
    "name": "bitpull_claim_database"
  }
}

Input Schema

NameRequiredDescriptionDefault
folderYesAbsolute path of the folder

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.3/5.0
Behavior3/5

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

The description adds meaningful behavior beyond the sparse annotation: the operation produces a time-limited link, targets the user's own Neon account, and concerns a temporary database. However, it does not explain authentication requirements, whether repeated calls create multiple links, whether existing links or databases are affected, or what exactly is returned.

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?

The definition is a single front-loaded sentence with no wasted wording. The key qualifier about the 15-minute link lifetime is included compactly.

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 tool that creates a time-limited claim link, the description covers the core purpose and lifetime but leaves several important gaps. With no output schema, it should more explicitly state what is returned and how repeated invocations behave.

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?

The schema already fully documents the single folder parameter as an absolute path. The description adds useful context that this folder corresponds to a site folder whose temporary database is being claimed, but it does not add further format or constraint details.

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?

The description states a specific action and resource: opening a link to claim the temporary Neon database of a site folder into the user's own Neon account. It is clear enough to distinguish this from generic folder or account tools, though it does not explicitly contrast with any sibling.

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?

There is no explicit guidance on when to use this tool, when not to use it, or what alternatives exist. The 15-minute link lifetime is useful context but is not framed as usage guidance or a prerequisite.

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