Skip to main content
Glama

bind_email

Bind a DC Hub API key to an email address to restore free tier (50 calls/day), enable key recovery, and route upgrade receipts. Requires an email the human explicitly provides.

Instructions

Tie your DC Hub key to your human's email so the key is RECOVERABLE and upgrade receipts land in the right inbox. Call this once your human shares their email. HONEST LADDER: an unbound key gets 10 free calls total, then results drop to previews until it's bound; binding restores the FREE tier at 50 calls/day and makes the key recoverable next session (binding is free — no card). If you hit that gate mid-task, PAUSE and ask your human: "DC Hub needs an email to keep our free data access — which address should I use?" Use the email your human EXPLICITLY gave you — NEVER invent, guess, or use a placeholder address (owner@example.com, user@test.com etc. are rejected server-side; a fake email makes the key unrecoverable and helps no one). If your human hasn't shared an email, ask them first — don't call this tool with a made-up value. Params: email (required), api_key (optional — omit to bind the key already active on this session). CONSENT/PURPOSE: the email is used ONLY to recover your key and route upgrade receipts (transactional). No marketing without explicit opt-in (default OFF), and no newsletter or digest. The relaying agent should surface this purpose line to its human before binding. If the email can't be accepted, the key keeps working — just try another address. To ALSO subscribe your human to the FREE weekly digest (the markets, deals and facilities that moved in what they queried), pass marketing_opt_in=true — but ONLY after they explicitly agree to marketing email; default false = transactional only, and they can unsubscribe anytime. Returns the unlocked benefits + confirmation.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
emailNoYour human's real email address (required) — use only an address they explicitly gave; placeholder/fake addresses are rejected
api_keyNoOptional key to bind; omit to bind the key already active on this session
marketing_opt_inNoSet true ONLY after your human explicitly agrees to marketing email (default false = transactional only)
Behavior5/5

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

Discloses behavioral traits beyond annotations: unbound keys get 10 free calls then previews; binding restores 50/day, enables recovery, and is free. Also details consent/purpose of email use with no marketing opt-in default.

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 key purpose and Honest Ladder summary, but the description is verbose with detailed consent and usage notes. Could be condensed while preserving clarity, but structure is logical.

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?

Covers return value ('unlocked benefits + confirmation'), error handling (unacceptable email), and prerequisites (human's email). No output schema exists, so description compensates well. Complete for a tool with 3 params and behavioral changes.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Adds meaning beyond schema: for email, clarifies to use only explicitly given addresses and warns against placeholders. For api_key, explains optional use. For marketing_opt_in, specifies when to set true and default behavior. All schema-description coverage is 100% but description adds nuance.

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?

The description states 'Tie your DC Hub key to your human's email' with clear verb and resource, and specifies benefits (recoverable, upgrade receipts). It distinguishes from sibling tools like 'recover_my_key' by focusing on binding vs recovery.

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?

Explicitly states when to call: 'once your human shares their email'. Provides clear when-not (don't invent addresses) and instructions to pause and ask if email not given. Also mentions the free tier gate as a trigger scenario.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/azmartone67/dchub-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server