Skip to main content
Glama
Sign In
API Hub MCP — 337+ Tools

API Hub MCP — 337+ Tools

by scotia1973-bot
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

wallet_create

Create a wallet to obtain an API key for the GadgetHumans credit system. Optionally provide an email for payment receipts.

Instructions

Create a new wallet and get an API key.

Use this to get started with the GadgetHumans credit system.
Your API key starts with 'gh_' and is used to authenticate AI tool calls.

Parameters:
    email — Optional email address for payment receipts.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "wallet_create"
  }
}

Input Schema

NameRequiredDescriptionDefault
emailNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.4.1

TDQS

A4.2/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full burden. It discloses the creation of a wallet and API key, the key prefix 'gh_', and the optional email parameter. However, it lacks details on side effects, idempotency, or whether authentication is required, which are important for a setup tool.

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 description is two sentences plus a single parameter line, with no unnecessary words. The main action is front-loaded, making it efficient and easy to parse.

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

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the simple tool with one optional parameter and an existing output schema, the description covers the essential purpose and usage context. It could mention potential duplicate creation behavior, but overall it is complete enough for an agent.

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 description coverage is 0%, so the description must add value. It explains the 'email' parameter is 'Optional email address for payment receipts,' which provides meaningful context beyond the schema's type and title.

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 clearly states 'Create a new wallet and get an API key,' specifying the verb (create), resource (wallet), and output (API key). It distinguishes from sibling tools like wallet_balance and wallet_buy, which operate on existing wallets.

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?

The description explicitly says 'Use this to get started with the GadgetHumans credit system,' indicating this is the first step. While it does not explicitly list when not to use it or name alternatives, the context from sibling names is clear.

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