Skip to main content
Glama

E-mail Signature Generator API - HTML signature from your details

email_signature_generator
Read-onlyIdempotent

Build a clean HTML e-mail signature (bar, simple or compact layout, accent colour) that works in Gmail and Outlook. Runs on our server, files are deleted right after the call, nothing stored. Free: 25 calls/day per IP. Paid: $0.002 per call via x402 at https://radarbg.com/x402/email-signature-generator.

Example tool call

This call uses example arguments supplied in the tool’s input schema.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "name": "Anna Example",
      "role": "Sales Manager",
      "email": "anna@example.com",
      "company": "Example Ltd",
      "website": "example.com"
    },
    "name": "email_signature_generator"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYesFull name
roleNoJob title
colorNoAccent colour HEX#2563eb
emailNoE-mail
phoneNoPhone
layoutNobar, simple or compactbar
addressNoAddress (optional)
companyNoCompany
websiteNoWebsite
linkedinNoLinkedIn link (optional)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Beyond the readOnlyHint/openWorldHint/idempotentHint annotations, the description discloses server-side execution, immediate file deletion and no storage, a 25 calls/day per-IP free cap, and a $0.002 per-call paid path via x402. These are exactly the operational facts an agent needs before spending a call; only the shape of the returned artifact is left implicit.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three sentences, front-loaded with the purpose before privacy and pricing details. The parenthetical variant list is slightly dense but every sentence carries distinct information; the pricing URL is long but functional.

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

Completeness4/5

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

For a 10-parameter generator with no output schema, the definition covers purpose, privacy, cost, and compatibility, and 'HTML signature' implies the return type. It stops short of stating the exact response payload or whether the HTML is returned inline versus as a file, which is the one remaining gap.

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 every one of the 10 parameters (including the layout enum) is already documented in the schema. The description only echoes the layout options and accent colour, adding no format, default, or validation detail beyond the structured fields, which is the expected baseline.

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 — build an HTML e-mail signature — and names the concrete variants (bar, simple, compact layout, accent colour) plus target clients (Gmail, Outlook). No sibling in the supplied list overlaps with signature generation, so an agent can route to this tool without ambiguity.

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

Usage Guidelines3/5

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

Usage is only implied: the agent must infer that this is the tool to reach for when a user needs an e-mail signature. There is no explicit when-to-use or when-not-to-use statement and no named alternative, though the pricing/free-tier note gives useful context for deciding whether to call it.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources