Skip to main content
Glama

Tillpad

by com.cnrcode
OverviewDiscussionsAdmin

bootstrap_agent

Start zero-human onboarding from an email address. Does not charge. Step 1: call with email. The result has verificationRequired=true and a 6-digit code is emailed to that address (10 minutes, single use), whether or not an account exists. Step 2: call again with email and code. Returns bootstrapToken, accountId, expiresIn, next, and machinePay (url, sku, amount). When you have no tp_ key yet, use REST POST /api/agents/bootstrap instead. The MCP endpoint requires Authorization: Bearer tp_… before any tool runs. After bootstrap, call manage_billing action=machine_pay, or POST /api/billing/machine-pay with Authorization: Bearer bootstrapToken. Use create_api_key afterward to mint run or sub keys from the resulting account tp_ key. No quota spend. Former name: agent_bootstrap.

Input Schema

NameRequiredDescriptionDefault
codeNo6-digit code from the verification email. Omit on the first call; required on the second.
emailYesAccount email. Required. Disposable domains are rejected. A verification code is sent to this address on the first call.
labelNoOptional label stored on the bootstrap account. Omit for none.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / code
      Added value: +{
+  "description": "6-digit code from the verification email. Omit on the first call; required on the second.",
+  "type": "string"
+}
    • changedInput schema / properties / email / description
      Previous value: -"Account email. Required. Disposable domains are rejected. No message is sent to this address."New value: +"Account email. Required. Disposable domains are rejected. A verification code is sent to this address on the first call."
  2. Added

TDQS

A4.8/5.0
Behavior5/5

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

No annotations exist, so the description carries the full burden and does so: it discloses no charge / no quota spend, a 10-minute single-use code, that a code is sent whether or not an account exists, the exact auth prerequisite (Bearer tp_… required before any tool runs), and the token-based auth for the follow-up billing call.

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?

Front-loaded with purpose and the step sequence, and most sentences carry unique operational value. The generic MCP auth line ('Authorization: Bearer tp_… before any tool runs') is boilerplate that applies to every tool and dilutes an otherwise dense, well-ordered description.

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?

There is no output schema, and the description compensates fully by enumerating the return payload (verificationRequired, bootstrapToken, accountId, expiresIn, next, machinePay with url/sku/amount). Auth, sequencing, alternatives, and follow-up calls are all covered, so an agent needs nothing else.

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?

Schema coverage is 100%, so baseline is 3, but the description adds meaning beyond the schema by tying the parameters to the two-call workflow and by explaining code behavior (emailed regardless of account existence, 10-minute expiry, single use). It does not add anything about the optional 'label' parameter, which keeps it from a 5.

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 — 'Start zero-human onboarding from an email address' — and immediately names the former name (agent_bootstrap) plus the sibling tools it feeds into (create_api_key, manage_billing). An agent can distinguish it from every sibling without opening a schema.

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 explicit two-step sequencing ('Step 1: call with email', 'Step 2: call again with email and code'), states when to avoid this tool ('When you have no tp_ key yet, use REST POST /api/agents/bootstrap instead'), and routes the agent onward to manage_billing and create_api_key.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Tillpad toolsInspect
Try in Browser
Context All Your Agents Can ShareAgents share what they learn, hand off work, and hold it when you switch models. Start with 5 GB free.fulcradynamics.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources