Skip to main content
Glama

Simulate inbound

simulate_inbound
Destructive

Sandbox only: simulate an inbound SMS to one of your test numbers (emits message.received; STOP, START and HELP act as for real).

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": {
      "from": "<from>",
      "body": "<body>"
    },
    "name": "simulate_inbound"
  }
}

Input Schema

NameRequiredDescriptionDefault
toNoOne of your sandbox numbers (never a live number). Optional while the account has one sandbox number.
bodyYesThe text of the simulated message
fromYesWho the simulated text comes from, in E.164

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / body / description
      Added value: +"The text of the simulated message"
    • addedInput schema / properties / from / description
      Added value: +"Who the simulated text comes from, in E.164"
  2. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already flag destructiveHint=true and openWorldHint=true; the description adds the crucial context that explains why — the call emits a message.received event and STOP/START/HELP keywords behave as real, meaning a simulated opt-out has real consequences. Still missing: what is returned (no output schema) and any prerequisite on account setup.

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 sentence with the scoping constraint front-loaded and the behavioral caveat in a compact parenthetical. No waste, 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?

Covers scope, side effects and keyword semantics for a 3-parameter tool whose inputs are fully described by the schema. The one gap is response shape — with no output schema, the description never says what the call returns, though this is minor for a simulation 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?

Schema coverage is 100%, so all three parameters are already documented, including the sandbox-number constraint on `to`. The description adds only that `body` content may be interpreted as a compliance keyword, which is useful but marginal against the schema baseline.

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 (simulate) and resource (inbound SMS), plus a hard scope constraint ('Sandbox only... one of your test numbers') that separates it from send_message and other delivery tools. An agent can identify this as a testing-simulation tool without inspecting the schema.

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?

'Sandbox only' clearly establishes the use case and implicitly excludes production use, which is the key routing decision. It does not explicitly name send_message as the production counterpart, so the alternative is inferred rather than stated.

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.