timps-swarm

timps_content_multiplier

Transform long-form technical posts into five short-form formats: tweet thread, LinkedIn post, changelog entry, docs blurb, and HN title. Set tone to technical, casual, or marketing.

Instructions

Transform a long-form technical post into multiple short-form formats: tweet thread, LinkedIn post, changelog entry, docs blurb, and HN title.

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": {
      "content": "<content>"
    },
    "name": "timps_content_multiplier"
  }
}

Input Schema

Name	Required	Description	Default
`tone`	No	'technical'\|'casual'\|'marketing'	technical
`content`	Yes	The long-form post or release notes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv2.2.1Aug 20, 2026

TDQS

A4/5.0

Behavior3/5

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

No annotations are provided, so the description carries the full burden. It explains the transformation from long-form to multiple short-form formats but does not disclose details such as output structure, how tone affects results, or whether all listed formats are always generated. This is a minor gap for a content transformation tool.

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 front-loads the primary action and quickly enumerates the output formats. Every word is purposeful with no redundancy.

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 simple tool with two params and no output schema, the description provides sufficient context: it clarifies input (long-form technical post) and expected outputs (five specific formats). However, it could be slightly more complete by confirming that all formats are produced or indicating how the tone parameter influences the output, but this is not critical.

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%, with both 'content' and 'tone' documented in the input schema. The description does not add extra parameter semantics beyond the schema, so the baseline of 3 is appropriate.

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 function with a specific verb (Transform) and resource (long-form technical post), listing concrete output formats (tweet thread, LinkedIn post, etc.). This distinguishes it from sibling tools by focusing on content repurposing.

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 clearly implies when to use this tool: when you have a long-form technical post and want to create short-form content. However, it does not explicitly mention alternatives or situations where another tool would be more appropriate, so it lacks a 'when not to use' clause.

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

Deploy Server