sigtap Agent Tools

email_template

Personalized cold email from proven templates Free check: https://sigtap-outreach-api.sigtap.workers.dev/preview/template = 200 demo sample, no wallet. Paid call: 402 challenge -> sign -> retry = settled on-chain. ($0.01 USDC on Base, x402)

Input Schema

TableJSON Schema

Name	Required	Description
`name`	No	Recipient name
`offer`	No	What you are offering
`company`	No	Recipient company
`persona`	No	founder \| agency \| freelancer

Output Schema

TableJSON Schema

Name	Required	Description	Default
`body`	Yes
`persona`	Yes
`subject`	Yes
`cadence_tips`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedSep 7, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "body": {
+      "type": "string"
+    },
+    "cadence_tips": {
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    "persona": {
+      "type": "string"
+    },
+    "subject": {
+      "type": "string"
+    }
+  },
+  "required": [
+    "persona",
+    "subject",
+    "body",
+    "cadence_tips"
+  ],
+  "type": "object"
+}

First observedSep 5, 2026

TDQS

A4.1/5.0

Behavior5/5

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

Discloses the two-tier access behavior: a free check returning a 200 demo without wallet, and a paid call involving a 402 challenge, signing, and retry, settled on-chain for $0.01 USDC. This transparency about cost and authentication exceeds typical description requirements.

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 brief and well-structured, breaking down the free and paid paths in a compact manner. No redundant or extraneous information.

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 existence of an output schema and clear parameter descriptions, the description is sufficient for an agent to understand the tool's function and invocation requirements, including the payment flow.

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 already provides descriptions for all four parameters (name, offer, company, persona) with 100% coverage. The tool description does not add additional parameter-level meaning, though the overall purpose is clarified.

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?

Clearly states it generates personalized cold emails from proven templates, and outlines both a free preview mode and a paid on-chain settlement mode. This distinguishes it from sibling tools like email_grade or deliverability_audit.

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

Usage Guidelines2/5

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

No explicit guidance on when to use this tool compared to siblings. The description focuses on the API access model (free vs paid) rather than use-case selection criteria.

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

All sigtap Agent Tools 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.