Skip to main content
Glama

Dial by Aloha Labs

manage_billing

Get a Stripe Customer Portal session URL. Your human opens it to update the card, switch between Starter, Pro and Scale, or cancel. Returns { url }.

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

Input Schema

NameRequiredDescriptionDefault
api_keyYesYour Dial API key (from sign_up)

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 burden and does disclose a key behavioral trait: the returned URL is meant for a human to open, not the agent to consume, and the response shape is { url }. It omits session lifetime/single-use semantics and whether each call mints a new session, which matter for retry and error handling.

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 and ending with the return shape. No filler or restated name/title content.

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?

Compensates well for having no output schema by naming the return value, and for having no annotations by explaining the human-in-the-loop handoff. Only session expiry/reusability behavior is missing for a fully complete picture of a one-parameter tool.

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?

Only one parameter (api_key) and the schema documents it at 100% coverage, including its source (sign_up). The description adds no further meaning about the parameter, 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 ('Get a Stripe Customer Portal session URL') and explains the downstream user action (update card, switch plan, cancel). It is clearly distinguishable from siblings like start_subscription and account_usage, which handle subscription creation and usage reporting rather than billing-portal access.

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 concrete triggering scenarios: when the human needs to update the card, change between Starter/Pro/Scale, or cancel. It doesn't explicitly name the sibling alternative (e.g., start_subscription for first-time purchase) or state when not to use it, so it stops short of full 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.