John's Essentials

email_file

Email My File — Email a finished file to the user themselves, with the file attached. It goes to the Google account they connected, so it appears in both their Sent folder and their inbox. The recipient is ALWAYS the current user — this tool cannot email anyone else and cannot send custom or user-authored content. Use ONLY when the user explicitly asks to have a result emailed to them. [category: utility]

Input Schema

TableJSON Schema

Name	Required	Description	Default
`file`	Yes	The file or files to email, typically the previous step's output. Several files are zipped into one attachment, so it is always one email.
`note`	No	Optional one-line note to put in the email body. The mail is sent from your own connected Google account, to you — files up to 5 MB.
`subject`	No	Subject line of the email.	Your file is ready

Schema Changelog

Changes observed during successful MCP inspections.

Changed4 schema fields changedSep 29, 2026

changedInput schema / properties / file / description

Previous value: -"The file to email — a file_id, typically the previous step's output."New value: +"The file or files to email, typically the previous step's output. Several files are zipped into one attachment, so it is always one email."

removedInput schema / properties / file / format
```
Removed value: -"binary"
```

addedInput schema / properties / file / items

Added value: +{
+  "format": "binary",
+  "type": "string"
+}

changedInput schema / properties / file / type

Previous value: -"string"New value: +"array"

Changed1 schema field changedSep 26, 2026
- addedInput schema / properties / note / x-ui
```
Added value: +{
+  "unset_label": "No note"
+}
```
Changed1 schema field changedSep 25, 2026
- addedInput schema / x-passes-no-file
```
Added value: +true
```

Changed3 schema fields changedSep 11, 2026

changedInput schema / properties / note / description

Previous value: -"Optional one-line note to include in the email body."New value: +"Optional one-line note to put in the email body. The mail is sent from your own connected Google account, to you — files up to 5 MB."

addedInput schema / properties / subject / default
```
Added value: +"Your file is ready"
```

changedInput schema / properties / subject / description

Previous value: -"Optional subject line. Defaults to 'Your file is ready'."New value: +"Subject line of the email."

First observedSep 5, 2026

TDQS

A4.7/5.0

Behavior5/5

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

Annotations only declare readOnlyHint=false and openWorldHint=true. The description adds real substance beyond that: the mail routes through the user's connected Google account, lands in both Sent and inbox, the recipient is always fixed, and no arbitrary content can be sent. The 5 MB size limit appears in the schema's note field.

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?

Front-loaded with the action and recipient, then constraints, then the usage gate. Every sentence carries a distinct piece of information with no filler.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

No output schema exists, but the description fully covers what happens after invocation (delivered to the user's own mailbox), the recipient constraint, the content constraint, and when to use it. Nothing an agent needs to call this correctly is missing.

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 file, note, and subject are all already documented in the schema. The description reinforces the fixed-recipient behavior but adds no syntax, format, or edge-case detail beyond what the schema fields provide. Baseline 3 applies when the schema does the heavy lifting.

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 and resource (email a finished file) plus the exact recipient scope (the user themselves, via their connected Google account). An agent can distinguish this from any convert/generate/upload sibling without opening a schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives an explicit trigger ("Use ONLY when the user explicitly asks to have a result emailed to them") and explicit exclusions (cannot email anyone else, cannot send custom or user-authored content). The when-not conditions are as clear as the when.

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

All John's Essentials 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?