Enpitech

Email AgentReady Report

email_agentready_report

Destructive

Emails the full 21-point AgentReady report for a site that has already been scanned, and stores the submitted name, email, phone and company as a sales lead in Enpitech's CRM under the agent-ready origin. The AgentReady view calls this tool when the user fills in the report form on the results page; it is not offered to the model. The scan is re-run server-side before the report is rendered, so the emailed report reflects the site at send time. Returns success with an emailed flag, which is false when the lead was stored but the email did not go out.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`url`	No
`name`	Yes
`email`	Yes
`phone`	No
`score`	No
`companyName`	No

Output Schema

TableJSON Schema

Name	Required	Description	Default
`emailed`	No	False when the request was stored but the email did not go out; the view then offers a PDF instead.
`success`	Yes	True when the request was stored.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedSep 26, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": false,
+  "properties": {
+    "emailed": {
+      "description": "False when the request was stored but the email did not go out; the view then offers a PDF instead.",
+      "type": "boolean"
+    },
+    "success": {
+      "description": "True when the request was stored.",
+      "type": "boolean"
+    }
+  },
+  "required": [
+    "success"
+  ],
+  "type": "object"
+}

First observedSep 26, 2026

TDQS

A4.7/5.0

Behavior5/5

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

Beyond annotations, the description discloses the server-side re-scan, the emailed flag semantics (false when lead stored but email fails), and the CRM side effect. This gives a complete picture of the tool's behavior and potential partial 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 well-structured: main action, usage context, then behavioral detail. Each sentence adds necessary information without repetition or fluff, making it concise and easy to parse.

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?

Given the output schema likely describes the return object, the description covers the key side effect (CRM lead), the freshness behavior (re-scan), and the email flag nuances. It is self-contained for an agent to use correctly.

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 0%, so the description must compensate. It mentions name, email, phone, and company as lead fields, but omits url and score entirely, leaving their purpose unclear. Partial compensation is provided but incomplete.

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 explicitly states the tool emails the full 21-point AgentReady report for an already-scanned site and stores lead info in CRM. It differentiates itself from siblings by noting it is not offered to the model, making its purpose unambiguous.

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?

Provides explicit when-to-use context (called by the AgentReady view on form submission) and a clear exclusion (not offered to the model). It also implies the prerequisite that the site has already been scanned, guiding appropriate invocation.

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

All Enpitech 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?