Skip to main content
Glama

Create account + API key

signup

Self-serve signup for an agent/app. Returns an API key ONCE. Save it as RENTADRIVER_API_KEY. Rehearse with a sandbox (rd_test_) key; live bookings need a funded wallet.

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

Input Schema

NameRequiredDescriptionDefault
kindNoagent
nameYes
emailYes
country_codeNoInitial country workspace. Enable additional countries with enable_country_workspace; each has its own local-currency balance.US
agent_frameworkNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior5/5

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

Beyond the annotations, the description discloses the critical non-obvious behavior: the API key is returned only ONCE and must be captured as RENTADRIVER_API_KEY. It also explains the sandbox key prefix (rd_test_) and that live bookings require a funded wallet, which is real operational context an agent cannot infer from the schema or annotations.

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 and the one-time return caveat. Every sentence adds a distinct, actionable fact with no filler.

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?

With no output schema, the description usefully explains the one thing that is returned (the API key) and the critical save-it-now constraint. But for a five-parameter creation tool, the input side is under-explained, and failure modes such as duplicate account or invalid email are not addressed.

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

Parameters2/5

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

Schema description coverage is only 20% across five parameters, so the description needs to compensate and does not. It says nothing about name, email, kind, or agent_framework; only country_code carries schema-level documentation. The mention of sandbox keys and wallet funding is behavior, not parameter meaning.

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 names a specific action and outcome: self-serve signup for an agent/app that returns an API key. The title 'Create account + API key' reinforces this. It stops short of explicitly distinguishing itself from the sibling create_api_key, which an agent could plausibly confuse it with.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

'Rehearse with a sandbox (rd_test_) key; live bookings need a funded wallet' gives useful context on the sandbox-to-live progression. However, there is no explicit statement of when to call this versus create_api_key or check_account_status, and no guidance on what to do if an account already exists.

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.