Skip to main content
Glama

Add inbound route

add_route

Forward incoming email for an address on a verified domain to an email address, an https URL or smtp://host:port. The domain MX record must point to KingSMTP. Paid plans only.

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": {
      "address": "<address>",
      "forward_to": "<forward_to>"
    },
    "name": "add_route"
  }
}

Input Schema

NameRequiredDescriptionDefault
addressYesFor example info@example.com
forward_toYesEmail address, https URL or smtp://host:port

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?

Annotations already declare readOnlyHint=false, destructiveHint=false and openWorldHint=true, so the safety profile is covered. The description adds genuinely useful prerequisites (MX record, verified domain, paid plan) that the annotations cannot convey, but it says nothing about conflict behavior when a route for the address already exists or about what is returned.

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?

Three short sentences, front-loaded with what the tool does and followed by the constraints that determine success. Nothing is repeated and no sentence is expendable.

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 two-parameter tool with no output schema and annotations covering the safety profile, the definition covers destination formats and all gating prerequisites. The only meaningful omission is behavior on duplicate addresses, which an agent would plausibly need before calling.

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%, including the accepted target formats and an example address, so the baseline is 3. The description only adds the constraint that the address must live on a verified domain whose MX points at KingSMTP, which is helpful context but not new per-parameter syntax.

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 states a specific action (forward incoming email for an address) plus the destination forms it supports, so the agent knows this creates an inbound routing rule rather than sending mail. It does not explicitly point at the counterpart tools (list_routes/delete_route), so sibling differentiation is implied by the resource rather than spelled out.

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?

Prerequisites are stated plainly: the domain must be verified, its MX record must point to KingSMTP, and the account must be on a paid plan. That tells the agent when the call will succeed, but there is no guidance on what to do when a route already exists for the address or on inspecting existing routes first.

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