Enpitech

Subscribe to Newsletter

subscribe_newsletter

Subscribes the email address the user typed into the newsletter signup view to the Enpitech newsletter, managed in Mailchimp. The newsletter view calls this tool when the user submits the form; it is not offered to the model. Returns success with a status of subscribed, or pending when a confirmation email was sent first. Every newsletter email carries an unsubscribe link.

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": {
      "email": "<email>"
    },
    "name": "subscribe_newsletter"
  }
}

Input Schema

Name	Required	Description	Default
`email`	Yes	The email address the user typed into the signup form.

Output Schema

Name	Required	Description	Default
`status`	No	subscribed, or pending when a confirmation email was sent first.
`success`	Yes	True when the signup went through.

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": {
+    "status": {
+      "description": "subscribed, or pending when a confirmation email was sent first.",
+      "enum": [
+        "subscribed",
+        "pending"
+      ],
+      "type": "string"
+    },
+    "success": {
+      "description": "True when the signup went through.",
+      "type": "boolean"
+    }
+  },
+  "required": [
+    "success"
+  ],
+  "type": "object"
+}

AddedSep 26, 2026

TDQS

A4.3/5.0

Behavior4/5

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

The description adds useful behavior beyond the annotations: it discloses that the result can be 'subscribed' or 'pending' depending on whether a confirmation email is sent first, and notes that every newsletter email includes an unsubscribe link. This gives an agent a realistic picture of side effects without contradicting the annotations.

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 three focused sentences: what the tool does, when it is invoked, and what outcomes/features to expect. Every sentence adds value, and the purpose is front-loaded rather than buried.

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?

With one well-documented parameter, an output schema, and annotations present, the description provides all necessary context: invocation origin, model non-availability, possible statuses, and a compliance note. Nothing an agent needs to correctly understand this tool 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?

The schema already describes the only parameter ('email') with full coverage, so the description does not need to add much. The description restates that the email comes from the signup form, but it does not add constraints, formats, or edge-case guidance beyond the 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 states a specific verb and resource: it subscribes the signup-view email to the Enpitech newsletter via Mailchimp. It also clarifies the tool's role by saying it is called by the newsletter view and not offered to the model, which differentiates it from the sibling 'newsletter' tool.

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?

The description explicitly states when the tool is invoked ('when the user submits the form') and that it is not offered to the model. It does not name alternative tools or give a when-not-to-use comparison, but the invocation context is clear enough for an agent to avoid selecting it directly.

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?