Skip to main content
Glama

Data Candy: US business leads

Create an account and API key

create_account

Create a Data Candy account and API key for an email address (free; credits start at $0). The key is shown once: store it. Returns the exact MCP configuration to reconnect with the key. If the email already has an account, no key is returned and its owner gets a sign-in link by email.

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": {
      "email": "<email>"
    },
    "name": "create_account"
  }
}

Input Schema

NameRequiredDescriptionDefault
emailYesEmail address that will own the account.
use_caseNoWhat you will use the leads for.
agent_nameNoName of your agent or app.
idempotency_keyNoOptional. Send the same value when retrying after a timeout so you are never charged twice for one purchase.

Output Schema

NameRequiredDescriptionDefault
accountNo
api_keyNoShown once. Store it now.
createdYes
messageYes
key_prefixNo
mcp_configNo
credits_usdNo
next_actionsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false, openWorldHint=true, so the safety profile is covered; the description adds real value beyond that by disclosing that the key is shown only once and must be stored, that creation is free, and that an existing-account email yields no key and instead triggers an email sign-in link. It does not address retry/idempotency behavior despite an idempotency_key parameter, which is the main remaining behavioral gap.

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 short sentences, front-loaded with the core action, then the critical operational warning (store the key), then the edge case. Every sentence carries distinct, non-redundant information.

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?

With an output schema present the description need not enumerate return values, yet it still flags that the response contains ready-to-use MCP configuration. Combined with the once-only key warning and the existing-account branch, an agent has everything needed to call it and handle both outcomes.

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?

Schema description coverage is 100%, so all four parameters (including use_case, agent_name, and idempotency_key) are already documented in the schema. The description adds meaning only for email, by explaining that ownership and the existing-account branch hinge on it; it says nothing extra about the other three parameters, so the baseline 3 applies.

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 ('Create a Data Candy account and API key') plus the scoping input ('for an email address'), which cleanly separates it from the sibling 'account_status' and from credit/lead tools. The branch for an email that already has an account further pins down exactly what the tool does and does not do.

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 use: an email address is required, the account is free, credits start at $0, and existing accounts get a sign-in link rather than a key. It stops short of naming alternatives or prerequisites (e.g., whether to check account_status first, or that add_credits is the follow-up for funding), so it is clear context without explicit exclusions.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources