Word Is Bond
Server Details
Test the voice agents you run: scored transcripts, pass/fail verdicts, latency and WER metrics.
- Status
- Healthy
- Last Tested
- Transport
- Streamable HTTP
- URL
Glama MCP Gateway
Connect through Glama MCP Gateway for full control over tool access and complete visibility into every call.
Full call logging
Every tool call is logged with complete inputs and outputs, so you can debug issues and audit what your agents are doing.
Tool access control
Enable or disable individual tools per connector, so you decide what your agents can and cannot do.
Managed credentials
Glama handles OAuth flows, token storage, and automatic rotation, so credentials never expire on your clients.
Usage analytics
See which tools your agents call, how often, and when, so you can understand usage patterns and catch anomalies.
Tool Definition Quality
Average 4.2/5 across 9 of 9 tools scored. Lowest: 3.6/5.
Each tool has a clearly distinct purpose. run_demo and run_test are differentiated by target (hosted demo vs. user's agent). The two verification tools form a clear two-step process. No overlap or ambiguity.
All tool names follow a consistent verb_noun pattern in snake_case (e.g., create_suite, get_trends, verify_number_start). No mixing of styles or vague verbs.
With 9 tools, the server is well-scoped for testing voice agents. Each tool covers a necessary operation without being excessive or too few.
The tool surface covers core workflows: suite CRUD (create/list, but no update/delete), testing (demo and real), trends, number verification, and recording setup. Minor gaps like missing suite deletion or an explicit tool to list all runs, but these are workable.
Available Tools
16 toolscreate_monitorInspect
Create a production monitor. "scenarioGoal" is what GOOD looks like for this agent — the judge scores every ingested call against it, exactly as a test scenario goal works. Optional "assertions" are plain-English checks the agent must satisfy. Read the ingest secret afterwards from GET /api/monitor/{id}/secret. Requires a pro or enterprise plan.
| Name | Required | Description | Default |
|---|---|---|---|
| name | Yes | Human name, e.g. "Support line — main agent". | |
| rubric | No | Extra free-text rubric appended to the judge instructions. | |
| language | No | BCP-47 language tag, default "en". | |
| assertions | No | Plain-English checks the agent must satisfy. | |
| sampleRate | No | Fraction 0..1 of ingested calls to score. Default 1 (score every call). | |
| scenarioGoal | Yes | What the agent is supposed to accomplish on every call. | |
| alertWebhookUrl | No | Optional public https URL to receive signed drift alerts. |
create_suiteInspect
Create a reusable test suite: a named set of scenarios/personas pinned to a target voice agent you run. Optionally give it a schedule ("weekly" | "daily" | "hourly", plan-gated) so it runs automatically and flags drift.
| Name | Required | Description | Default |
|---|---|---|---|
| name | Yes | ||
| language | No | BCP-47 language tag, default "en". | |
| schedule | No | Cadence for scheduled runs, e.g. "weekly" | "daily" | "hourly". | |
| scenarios | No | Persona + goal pairs the suite exercises. | |
| targetAgent | Yes | The voice agent under test — a system you run. transport "direct" (SIP/WebRTC) has near-zero cost and works on every plan; "pstn" places a real carrier call (pro+ plans) and only to a number you have verified. The hosted demo target is { "transport": "direct", "peerId": "wb-demo-dental" }. |
diff_flowInspect
Show the structural diff between two versions of a version-controlled flow: which nodes and edges were added, removed, or changed. This is the code review for your phone system — see exactly what a change did before you ship it.
| Name | Required | Description | Default |
|---|---|---|---|
| to | No | Target version number (defaults to the current version). | |
| from | Yes | Base version number. | |
| flowId | Yes | The flow id. |
get_monitor_healthInspect
Read a monitor's live rolling health and drift. Health is unknown | healthy | degraded | critical. Drift is isolated by judge version: when our judge changes, the boundary is reported as judgeVersionChanged and NEVER as an agent regression — a score delta across that boundary says nothing about your agent.
| Name | Required | Description | Default |
|---|---|---|---|
| monitorId | Yes | The monitor to read. |
get_trendsInspect
Read account-wide testing trends over a window: pass-rate, average score, and run-to-run regressions per suite, plus overall totals. Use this to spot behaviour drift in the voice agents you test.
| Name | Required | Description | Default |
|---|---|---|---|
| days | No | Look-back window in days (default 90). |
import_flowInspect
Import a phone-system flow or voice-agent config from a platform (e.g. Vapi) into the canonical, diffable Flow IR — the first step of putting your phone system under version control. Reports the fields the IR abstracts away. Pass save:true to persist it as a versioned flow. The same IR exports back out, so it doubles as a migration surface between platforms.
| Name | Required | Description | Default |
|---|---|---|---|
| name | No | Name for the saved flow (defaults to the config name). | |
| save | No | Persist the imported IR as a new versioned flow. | |
| config | Yes | The platform's native flow/agent object. | |
| platform | Yes | The source platform. |
ingest_callInspect
Send one completed PRODUCTION call to a monitor to be scored. Returns 202 immediately; scoring runs in the background and the monitor health updates. The transcript is scored in flight and never stored — only the scorecard and safe metadata are kept. Pass "externalId" (your own call id) so a re-delivered call scores exactly once.
| Name | Required | Description | Default |
|---|---|---|---|
| platform | No | Where the call ran, e.g. "retell", "vapi", "telnyx". | |
| monitorId | Yes | The monitor to ingest into. | |
| externalId | No | Your own call id — makes the ingest idempotent. | |
| occurredAt | No | ISO-8601 timestamp of when the call happened. | |
| transcript | Yes | Formatted "AGENT: … / CALLER: …" transcript of the finished call. | |
| durationSec | No | Call duration in seconds. |
list_monitorsInspect
List your production monitors and their current health (unknown | healthy | degraded | critical). A monitor watches ONE live production line: you stream it completed calls, and it scores each with the same versioned judge that scores your tests, tracks a rolling baseline, and alerts when quality drifts. Requires a pro or enterprise plan.
| Name | Required | Description | Default |
|---|---|---|---|
No parameters | |||
list_suitesInspect
List your reusable test suites (each is a set of scenarios/personas pinned to a target voice agent). Returns their ids, names, targets, and schedules — use a suite id with run_test or get_trends.
| Name | Required | Description | Default |
|---|---|---|---|
No parameters | |||
list_verified_numbersInspect
List the phone numbers your account has proven it controls. Only these numbers (and Word Is Bond DIDs) may be used as a "pstn" targetAgent.toNumber. Revoke one with DELETE /api/numbers/{id}.
| Name | Required | Description | Default |
|---|---|---|---|
No parameters | |||
register_recording_targetInspect
Register where BYOS call recordings go, so you can pass "record": true to run_test and have that call’s audio teed to YOUR OWN storage. wordis-bond keeps only a pointer (the run’s recording_url), never the audio. "callbackUrl" is a public https endpoint that returns a presigned PUT URL per recording (so wordis-bond never holds your cloud credentials). Pro/enterprise capability, bundled free — you pay your own storage; starter → 402.
| Name | Required | Description | Default |
|---|---|---|---|
| name | Yes | A label for this target. | |
| track | No | Which side to capture (default inbound = the agent). | |
| callbackUrl | Yes | Public https endpoint that mints a presigned PUT URL per recording. |
run_demoInspect
Run the hosted demo voice agent (a dental front desk) end-to-end and get a real, fully-scored result in about a minute — no target of your own needed. Returns the score (0–100), pass/fail verdict, per-turn metrics, the transcript, and a shareable public report URL. Zero carrier cost. Optional inputs override the scenario.
| Name | Required | Description | Default |
|---|---|---|---|
| goal | No | What the synthetic caller should try to accomplish. | |
| bargeIn | No | Inject one caller-initiated barge-in. | |
| persona | No | Override the synthetic caller persona. | |
| expected | No | Expected agent lines to pin for word-error-rate. | |
| language | No | BCP-47 language tag, default "en". |
run_testInspect
Run a test against a voice agent you control. Two modes: (1) score a captured transcript offline — pass "transcript" (or "turns") plus "scenarioGoal"; the judge returns a scored run synchronously. (2) run a live synthetic call — pass "targetAgent" and "goal". A live "direct" (SIP/WebRTC) target returns a tokenized media WebSocket URL for your agent-side harness to dial; a "pstn" target places a real carrier call (pro+ plans) to a number you have verified — an unverified destination returns 403 NUMBER_NOT_VERIFIED and no call is placed. Poll get_run / GET /api/tests/{id} for the terminal scored state of a live run.
| Name | Required | Description | Default |
|---|---|---|---|
| goal | No | What the synthetic caller should accomplish (live mode). | |
| turns | No | Per-turn capture; formatted into a transcript when "transcript" is omitted. | |
| record | No | Record this call to YOUR OWN storage (BYOS, default false). Requires the byosRecording capability (pro/enterprise) and an enabled recording target; the customer-owned pointer comes back in the run’s recording_url. wordis-bond keeps only the pointer, never the audio. | |
| bargeIn | No | ||
| persona | No | The synthetic caller persona (live mode). | |
| suiteId | No | Link this run to a suite (optional). | |
| expected | No | ||
| language | No | BCP-47 language tag, default "en". | |
| transport | No | Force a transport (live mode). | |
| assertions | No | Extra pass/fail checks for the judge. | |
| transcript | No | Captured conversation to score (offline mode). | |
| concurrency | No | Number of parallel live calls. | |
| targetAgent | No | The voice agent under test — a system you run. transport "direct" (SIP/WebRTC) has near-zero cost and works on every plan; "pstn" places a real carrier call (pro+ plans) and only to a number you have verified. The hosted demo target is { "transport": "direct", "peerId": "wb-demo-dental" }. | |
| scenarioGoal | No | What the conversation was meant to accomplish (offline mode). | |
| recordTargetId | No | Record to THIS target (else the most-recent enabled one). |
test_flowInspect
Run the regression gate on a flow now: compile the current version into a synthetic-caller test, run it against the flow's target, and compare the result to the previous version's baseline. A behavior change that regressed (a pass turning into a fail, or a score drop past the threshold) is caught and blocks the change — continuous integration for your phone-system logic.
| Name | Required | Description | Default |
|---|---|---|---|
| flowId | Yes | The flow id to gate. |
verify_number_confirmInspect
Finish verifying a phone number by supplying the 6-digit code spoken on the verification call. On success the number becomes a permitted PSTN test destination for your account. The code is single-use, expires after ten minutes, and locks after five incorrect attempts.
| Name | Required | Description | Default |
|---|---|---|---|
| code | Yes | The 6 digits spoken on the call. | |
| label | No | Optional label stored alongside the verified number. | |
| number | Yes | The number being verified, in E.164. |
verify_number_startInspect
Prove your account controls a phone number, which it must do before any PSTN test call to it. Word Is Bond places one short call to the number, speaks a 6-digit code twice, and hangs up. Confirm the code within ten minutes with verify_number_confirm. Calling an already-verified number places no call. This is the only action that dials an unverified number and it is tightly capped (3 calls per number and 5 distinct numbers per account, per day).
| Name | Required | Description | Default |
|---|---|---|---|
| number | Yes | The number to verify, in E.164 (e.g. "+15045204977"). |
Claim this connector by publishing a /.well-known/glama.json file on your server's domain with the following structure:
{
"$schema": "https://glama.ai/mcp/schemas/connector.json",
"maintainers": [{ "email": "your-email@example.com" }]
}The email address must match the email associated with your Glama account. Once published, Glama will automatically detect and verify the file within a few minutes.
Control your server's listing on Glama, including description and metadata
Access analytics and receive server usage reports
Get monitoring and health status updates for your server
Feature your server to boost visibility and reach more users
For users:
Full audit trail – every tool call is logged with inputs and outputs for compliance and debugging
Granular tool control – enable or disable individual tools per connector to limit what your AI agents can do
Centralized credential management – store and rotate API keys and OAuth tokens in one place
Change alerts – get notified when a connector changes its schema, adds or removes tools, or updates tool definitions, so nothing breaks silently
For server owners:
Proven adoption – public usage metrics on your listing show real-world traction and build trust with prospective users
Tool-level analytics – see which tools are being used most, helping you prioritize development and documentation
Direct user feedback – users can report issues and suggest improvements through the listing, giving you a channel you would not have otherwise
The connector status is unhealthy when Glama is unable to successfully connect to the server. This can happen for several reasons:
The server is experiencing an outage
The URL of the server is wrong
Credentials required to access the server are missing or invalid
If you are the owner of this MCP connector and would like to make modifications to the listing, including providing test credentials for accessing the server, please contact support@glama.ai.
Discussions
No comments yet. Be the first to start the discussion!