Whisper

Get a Whisper API key

whisper_signup

Start or complete Whisper signup from an email address alone, and receive an API key that unlocks the provisioning and governance skills on this card. Send {"email":"..."} to start; a six-digit code arrives by email; send {"signup_id":"...","code":"123456"} to complete. No human step, no account needed first. Example call: {"skill":"signup","input":{"email":"agent@example.com"}}

Input Schema

TableJSON Schema

Name	Required	Description	Default
`input`	Yes	Arguments for this operation, as an object. The example passes {"email":"agent@example.com"}.

Output Schema

TableJSON Schema

Name	Required	Description
`ok`	Yes	Whether the step succeeded.
`api_key`	No	Returned by the second step. This is the credential; send it as the X-API-Key header and the provisioning and governance tools appear in tools/list.
`message`	No	What to do next, in a sentence.
`signup_id`	No	Returned by the first step. Send it back with the six-digit code from the email to finish.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedSep 25, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "description": "The result of a signup step: an id to continue with, or the API key itself.",
+  "properties": {
+    "api_key": {
+      "description": "Returned by the second step. This is the credential; send it as the X-API-Key header and the provisioning and governance tools appear in tools/list.",
+      "type": "string"
+    },
+    "message": {
+      "description": "What to do next, in a sentence.",
+      "type": "string"
+    },
+    "ok": {
+      "description": "Whether the step succeeded.",
+      "type": "boolean"
+    },
+    "signup_id": {
+      "description": "Returned by the first step. Send it back with the six-digit code from the email to finish.",
+      "type": "string"
+    }
+  },
+  "required": [
+    "ok"
+  ],
+  "type": "object"
+}

First observedSep 24, 2026

TDQS

A4.5/5.0

Behavior4/5

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

Annotations already indicate this is not read-only and not destructive, which lowers the bar. The description adds meaningful behavioral detail: an email is sent, a code is delivered, a key is issued, and the key unlocks certain skills. Nothing contradicts the annotations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is compact and front-loaded with the core purpose, then follows with the operative protocol and an example. Every sentence contributes necessary information; the only minor extra is the phrase 'on this card,' which is harmless platform context.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a two-step signup flow, the description fully explains prerequisites, the payloads for each step, and the expected result of receiving an API key. Since an output schema exists, the absence of return-value details is appropriate. An agent has all the information needed to invoke this tool correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The schema only provides a generic 'input' object, so the description carries the full semantic load. It gives the exact payload shapes for both phases—{'email':'...'} and {'signup_id':'...','code':'123456'}—plus a concrete example call. This goes well beyond what the input schema alone communicates.

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?

The description states a specific, observable outcome: start or complete Whisper signup from an email address and receive an API key. It also conveys the two-phase nature of the operation, which clearly separates it from the read/lookup-focused sibling tools.

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 description provides a concrete invocation path: send an email first, receive a six-digit code, then send the signup_id and code to complete. It also clarifies that no human step or prior account is needed. It does not explicitly name alternatives, but no sibling appears to offer signup functionality, so the omission is minor.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Whisper tools Inspect

Try in Browser

Context Every Agent Can ShareAgents share what they learn, hand off work, and keep it when you switch models. Start with 5 GB free.fulcradynamics.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.