shiply

Send an email from a site

send_email

Send an email from .shiply.now's managed sender. The site can send transactional/notification email — no SMTP setup. Rate-limited and spam-checked; replies route back to the site inbox.

Input Schema

TableJSON Schema

Name	Required	Description
`to`	Yes	recipient email address
`html`	Yes	email HTML body
`slug`	Yes	site slug to send from (<slug>.shiply.now sender)
`text`	No	plain-text fallback body
`subject`	Yes	email subject line

Output Schema

TableJSON Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed6 schema fields changedJun 23, 2026

addedInput schema / properties / html / description
```
Added value: +"email HTML body"
```

addedInput schema / properties / slug / description

Added value: +"site slug to send from (<slug>.shiply.now sender)"

addedInput schema / properties / subject / description
```
Added value: +"email subject line"
```
addedInput schema / properties / text / description
```
Added value: +"plain-text fallback body"
```
addedInput schema / properties / to / description
```
Added value: +"recipient email address"
```

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": false,
+  "properties": {
+    "result": {}
+  },
+  "required": [
+    "result"
+  ],
+  "type": "object"
+}

First observedJun 23, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Adds behavioral details beyond annotations: rate-limited and spam-checked, plus reply routing. Annotations only provide openWorldHint and idempotentHint. The description adds operational constraints and side effects.

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?

Two clear, front-loaded sentences. First states core action, second adds key context. No redundant information.

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?

Given the tool's complexity (5 params, 4 required), the description covers purpose, usage context, and behavioral traits adequately. Output schema exists, so return value explanation is not required.

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 description coverage is 100%, so baseline is 3. Description adds marginal value by connecting slug to the sender domain and mentioning reply behavior, but doesn't enhance parameter understanding beyond schema.

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 clearly states the action (Send) and resource (email from a site's managed sender), specifying transactional/notification email. It differentiates from sibling tools like send_broadcast by emphasizing transactional nature.

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?

Provides context: no SMTP setup needed, rate-limited, spam-checked, and replies route to site inbox. While it doesn't explicitly state when not to use, it implies suitability for individual transactional emails, distinguishing from broadcast siblings.

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

All shiply tools Inspect

Try in Browser

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?