Skip to main content
Glama

Dial by Aloha Labs

resend_confirmation_email

Send a new email-confirmation link to your account's address (if the first one expired or got lost).

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

Input Schema

NameRequiredDescriptionDefault
api_keyYesYour Dial API key (from sign_up)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior3/5

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

No annotations exist, so the description carries the full burden. It usefully discloses that the recipient is fixed to the account's address (no email parameter needed), but says nothing about whether the prior link is invalidated, rate limiting, or failure modes such as an unverified/nonexistent account.

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?

A single front-loaded sentence with the action first and the qualifying condition in parentheses. Nothing wasted, nothing buried.

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 one-parameter, no-output-schema tool this is largely sufficient: an agent knows what it does and when. The remaining gap is side-effect disclosure (link invalidation, resend throttling), which matters for a mail-sending operation.

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 and schema coverage is 100%, so the api_key field is already fully documented as coming from sign_up. The description adds no further syntax or format detail, but the schema baseline already covers it.

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?

States a specific verb (send/resend) and resource (email-confirmation link) and clarifies the destination is the account's own address. That implicitly separates it from sign_up and wait_for_verification_code, though no sibling is named 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?

The parenthetical '(if the first one expired or got lost)' gives a concrete trigger condition for when to call it. It stops short of naming alternatives or exclusions (e.g., what to do instead when no sign_up has occurred yet).

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.