Skip to main content
Glama

Dial by Aloha Labs

sign_up

Create your own Dial account. Use an email inbox you can read: a confirmation link is sent there and must be opened before you can get a number. Returns your api_key ONCE. Store it somewhere permanent and pass it to the other tools.

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": "sign_up"
  }
}

Input Schema

NameRequiredDescriptionDefault
emailYesAn email address you can read
invite_codeNoInvite code (required during the private beta)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

With no annotations, the description carries the full load and does well: it discloses the email-confirmation gate, that api_key is returned only ONCE, and that the key must be persisted and passed to other tools — critical behavior an agent cannot infer from the schema. It stops short of stating what happens on duplicate email, whether the invite_code is currently mandatory, or how errors surface.

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 action, then the blocking prerequisite, then the one-time secret warning. Every sentence carries information the agent needs and none is wasted.

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?

For a two-parameter, no-output-schema tool the description covers the essentials: what it creates, what the agent must supply, the confirmation dependency, and the critical return value (api_key) with its one-time nature. The invite_code beta requirement and post-signup state transitions are left entirely to the schema and inference.

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 coverage is 100%, so both parameters are already documented, including that invite_code is required during the private beta. The description reinforces the email constraint ('an inbox you can read') but adds nothing about invite_code beyond what the schema says, so the baseline of 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 your own Dial account') and no sibling among the twelve does the same thing, so it is immediately distinguishable from account_usage, manage_billing, and the rest. The follow-on sentence about getting a number clarifies the account's purpose in the product.

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 a concrete precondition for use ('an email inbox you can read') and explains the blocking step (confirmation link must be opened before you can get a number). It does not name the closely related sibling resend_confirmation_email as the recovery path if the link is lost, which is the one missing piece of routing guidance.

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.