Skip to main content
Glama
Sign In
timps-swarm

timps-swarm

by Sandeeprdy1729
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

timps_cold_email_sequence_writer

Write a 5-7 step cold-outreach email sequence with subject A/B variants, social proof, objection handling, and reply-promise CTA for a persona and offer, ensuring spam-safe deliverability.

Instructions

Write a 5-7 step cold-outreach email sequence for a persona + offer, with subject A/B variants, social proof, objection handling, and a reply-promise CTA. Spam-safe.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "timps_cold_email_sequence_writer"
  }
}

Input Schema

NameRequiredDescriptionDefault
requestNoPlain-English task or context for the agent.
languageNoPrimary programming language (default: python).python

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.2.1

TDQS

C2.9/5.0
Behavior1/5

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

No annotations are provided, and the description does not disclose any behavioral aspects such as permissions, side effects, rate limits, or whether it sends emails or just generates content. The mention of 'spam-safe' is a feature, not a transparency disclosure.

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 a single, well-structured sentence that efficiently conveys all key features without unnecessary fluff.

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

Completeness3/5

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

The description covers the main purpose and output elements but lacks information about the output format (since there's no output schema) and any prerequisites or context needed to use the tool effectively.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The input schema descriptions are minimal. The tool description does not add clarity to the 'request' parameter (e.g., what details like persona and offer should be included) or the 'language' parameter, which is confusingly described as a programming language despite being used for email sequences.

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 clearly states the tool's purpose: writing a 5-7 step cold-outreach email sequence. It specifies key elements like persona, offer, subject variants, social proof, objection handling, CTA, and spam-safe, making it distinct from other technical tools.

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?

The description does not provide explicit guidance on when to use this tool versus alternatives. It only describes what it does, without mentioning conditions, scenarios, or comparisons to other tools.

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

Deploy Server

Other Tools