Email

email: 8 operations.

Also for this capability: API · CLI · MCP · SDKs

email: 8 operations. Name one in "op" and pass that operation's own arguments in "input". describe returns an operation's input schema.

Tool	`email`
Address	`https://api.hanzo.ai/v1/mcp`
Method	`tools/call` (JSON-RPC 2.0)
Arguments	2, 1 required
Operation	`GET /v1/email/{id}` · `GET /v1/email/sendgrid/status` · `GET /v1/email/ses/status`
Product	email

Arguments

Field	Type	Required	Default	Values	Description
`input`	`object`	—	—	—	arguments for the chosen op
`op`	`string`	yes	—	—	—

tools/list declares a type, a description, which fields are required and an enumerated value set for each field and nothing further, and every column above is MCP's own. This tool takes an operation name and that operation's arguments, so what the document constrains is what goes inside input, field by field, on the operation you name — ask describe for that. A — means MCP does not constrain the field.

Call it

A tools/call carries every argument in one flat object — nothing binds to a path or a query string. This call carries exactly the arguments the operation requires, so it is the smallest one that can run.

curl -X POST https://api.hanzo.ai/v1/mcp \
  -H "Authorization: Bearer $HANZO_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
       "jsonrpc": "2.0",
       "id": 1,
       "method": "tools/call",
       "params": {
         "name": "email",
         "arguments": {
           "op": "list_emails"
         }
       }
     }'

Values are the operation's own defaults and enumerated values where it declares them, and a <placeholder> where neither source declares one. tools/list needs no credential; tools/call does — called without one MCP answers HTTP 200 with a JSON-RPC result whose isError is set and whose text says what was missing. How to get a key →

The operation behind it

email dispatches to 8 operations. 3 of them MCP names exactly as the document ids them, and those are below; for the rest MCP has its own verb, which describe resolves.

Operation	Route	Product	Summary
`get_email_by_id`	`GET /v1/email/{id}`	email	Reads one message of the org's ledger, sent through this API or told of by its provider, with what became of it.
`get_email_sendgrid_status`	`GET /v1/email/sendgrid/status`	email	Reports the org's SendGrid configuration: whether it holds the credentials a send needs, the account's credits as SendGrid answers them, what the org's ledger counted sent by SendGrid in the last 24 hours, and the DNS records of the sending domain.
`get_email_ses_status`	`GET /v1/email/ses/status`	email	Reports the org's Amazon SES configuration: whether it holds the credentials a send needs, the account's limits as SES answers them (sandbox, sending enabled, 24-hour quota, rate, sent in the last 24 hours), what the org's ledger counted sent by SES in the last 24 hours, and the DNS records of the sending domain.

The same capability over plain HTTP is in the email API reference, on https://api.hanzo.ai.

All 127 tools · MCP · API reference

Generated from tools/list on https://api.hanzo.ai/v1/mcp — 127 tools captured 2026-11-10.

Was this page useful?

Broken link or missing step? Drop it in #docs on Discord or open a PR.

PreviousDomain NextEngine