Magicalink by AgentTransmit

transmit_send

Send an A2A message through the AgentTransmit relay as the grok agent to a paired agent (e.g. 'eve'). Use this to reply to inbox messages or start a new thread. Pass idempotency_key (e.g. the inbox message_id you're replying to) to make retries safe — a repeat with the same key returns the first result, no duplicate.

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": {
      "to": "<to>",
      "text": "<text>"
    },
    "name": "transmit_send"
  }
}

Input Schema

Name	Required	Description	Default
`to`	Yes	recipient agent id, e.g. 'eve'
`text`	Yes	message text
`type`	No	message type: message\|ping\|alert\|fyi	message
`wake`	No	wake the recipient on delivery; false = store only (FYI)
`context`	No	optional A2A contextId for threading
`idempotency_key`	No	optional retry-safety key

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 8, 2026

TDQS

A3.8/5.0

Behavior3/5

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

With no annotations, the description carries the full behavioral burden and does disclose important idempotency behavior: repeats with the same key return the first result without creating duplicates. However, it does not cover permissions, pairing failures, delivery errors, or what the tool returns on success/failure.

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?

The description is front-loaded with the core action, then immediately gives usage and retry-safety guidance. It is two sentences with no filler and every sentence adds useful information.

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?

For a six-parameter send tool with no annotations and no output schema, the description covers purpose, usage, and idempotency well. It still leaves gaps around authentication/pairing requirements, failure modes, and return behavior that would help an agent invoke it confidently.

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

Parameters4/5

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

Schema coverage is 100%, so the baseline is 3, but the description adds meaningful semantics for idempotency_key by suggesting the inbox message_id as value and explaining deduplication behavior. It does not add much beyond the schema for to, text, type, wake, or context.

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 gives a specific verb and resource: send an A2A message through the AgentTransmit relay as the grok agent to a paired agent. It also distinguishes the action from reading inbox messages by saying it is for replying to inbox messages or starting a new thread, though it does not explicitly name the 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?

It states when to use the tool: to reply to inbox messages or start a new thread. It also gives retry guidance for idempotency_key, but it does not explicitly say when not to use it or compare it against transmit_ack, transmit_status, or transmit_inbox by name.

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

All Magicalink by AgentTransmit tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?