Skip to main content
Glama

aui_share_widget

Deliver a generated AUI visualization (cache_id) directly to a phone number via Twilio A2P SMS or email address via Mailgun.

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": {
      "aui_api_key": "<aui_api_key>",
      "cache_id": "<cache_id>",
      "method": "<method>",
      "to": "<to>"
    },
    "name": "aui_share_widget"
  }
}

Input Schema

NameRequiredDescriptionDefault
toYesRecipient phone number (+1...) or email address.
methodYesDelivery channel.
messageNoOptional note (paid keys only).
cache_idYesThe chk_... cache_id returned by aui_generate_ui.
aui_api_keyYesAUI trial or paid API key.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.3/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full disclosure burden, yet it says nothing about externally visible side effects: outbound SMS/email is sent through third-party providers (Twilio A2P, Mailgun), which implies costs, carrier/rate limits, and possible delivery failure. It also does not mention permission or key-tier constraints or what a successful send returns, leaving an agent unable to predict the consequences of calling it.

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 no filler: the action, the artifact, the two providers and the recipient types are all packed in without redundancy.

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 and no annotations, the definition leaves notable gaps for a 5-parameter tool that dispatches real messages: no return value, no failure/retry behavior, and no statement of cost or rate constraints. The core selection signal is adequate, but an agent could not fully predict outcomes from the description alone.

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 description coverage is 100%, so all five parameters, including the sms/email enum and the paid-key caveat on 'message', are already documented in the schema. The description only restates that 'to' is a phone number or email and adds no format, validation, or tier nuance beyond that, which is the baseline case.

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 pairs a specific verb ('Deliver') with a specific resource ('a generated AUI visualization (cache_id)') and enumerates the two delivery channels (Twilio A2P SMS, Mailgun email). That is enough to separate it from siblings like aui_generate_ui or aui_claim_free_trial, though the description never names those siblings as alternatives.

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?

Usage is only implied: by tying the input to a 'generated AUI visualization (cache_id)', it hints that this is the step after aui_generate_ui, but it never states when to choose SMS vs email, when not to call it, or any prerequisites such as needing a paid key to use the message field.

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.

Resources