Skip to main content
Glama

Dial by Aloha Labs

start_subscription

Get a Stripe Checkout link for a monthly plan. starter is $15 (1 number, 100 call minutes, 400 SMS), pro is $49 (5 numbers, 250 minutes, 1,000 SMS), scale is $179 (20 numbers, 1,000 minutes, 5,000 SMS). Your human can enter a promotion code on the page. Extra minutes are $0.15, extra numbers $2, extra SMS $0.015. Give the link to your human.

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": {
      "api_key": "<api_key>"
    },
    "name": "start_subscription"
  }
}

Input Schema

NameRequiredDescriptionDefault
planNostarter ($15), pro ($49) or scale ($179). Default starter.
api_keyYesYour Dial API key (from sign_up)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/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 burden and does disclose key behavior: this returns a link rather than charging, the human completes payment and can apply a promo code, and extra usage is billed per unit. It omits whether repeated calls create multiple links, link expiry, or error behavior for already-subscribed accounts.

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?

Purpose is front-loaded in the first sentence, followed by tier contents, promo behavior, overage pricing, and the required agent action. Dense but every sentence carries information the agent must relay to its human; nothing is redundant.

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?

No output schema exists, and the description compensates by explaining that the return value is a Stripe Checkout link to be handed to the human. Combined with full schema coverage and tier/overage pricing, it is nearly complete for a 2-parameter tool; only lifecycle/edge-case behavior is missing.

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 coverage is 100% and the plan enum is already documented, so the baseline would be 3. The description adds real meaning beyond the schema by spelling out what each tier includes (numbers, minutes, SMS) and the per-unit overage rates, which the schema's one-line tier pricing does not cover.

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 opens with a specific verb and artifact: "Get a Stripe Checkout link for a monthly plan." That distinguishes it in kind from siblings like manage_billing (account/billing changes) and account_usage (inspection), though it never names an alternative explicitly.

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?

It gives clear usage direction — "Give the link to your human" — and notes the human can enter a promotion code on the page, which frames this as a human-in-the-loop flow rather than an automated charge. It does not state when not to use it (e.g., if a subscription 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.