Skip to main content
Glama

Thread Kit: posts that fit every network

Split text into a thread that fits (X, Bluesky, Farcaster, Mastodon, Threads) ($0.002)

split_thread
Read-onlyIdempotent

Split long text into a thread where every post fits the network's limit, counted the way that network counts. X: weighted, CJK and emoji count 2, every link 23, limit 280. Bluesky: 300 graphemes and 3000 bytes. Farcaster: UTF-8 bytes, 320 per cast (1024 long cast). Mastodon: 500, links 23. Threads (Meta): 500, emoji count as their UTF-8 bytes. Breaks at paragraph, sentence, clause, then word boundaries (CJK-aware), never inside a URL or @mention, adds n/N numbering that is included in the count, and re-checks every post. Returns posts with their lengths. Pure computation. PAID: $0.002 per call in USDC on Base via x402 over MCP, or from prepaid credits if this server is configured with an Authorization: Bearer tkc_... header (see payment_options).

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": {
      "text": "<text>"
    },
    "name": "split_thread"
  }
}

Input Schema

NameRequiredDescriptionDefault
textYesThe text to split (any language, max 25000 characters)
limitNoOptional max length per post in that network's unit; default is the network's own limit (see network_rules)
networkNoTarget network: x (X/Twitter, default), bluesky, farcaster, mastodon or meta-threads (Threads by Meta)
numberingNoWhere to put "n/N": suffix (default), prefix or none; counted in each post's length

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, closed-world and non-destructive, so the lower bar applies, yet the description still adds real behavioral context: exact splitting precedence (paragraph, sentence, clause, word, CJK-aware), the guarantee it never breaks inside a URL or @mention, numbering included in the count, and a post-hoc re-check. It also discloses cost ($0.002 via x402 or prepaid Bearer credits), which is behavior an agent must know before calling.

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?

Front-loaded with the purpose, then the per-network rules, then the splitting behavior, then payment. Dense but nearly every clause carries information an agent needs. The payment sentence is long and could be compressed, and the network rule list reads as one run-on block.

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?

For a pure-computation tool with no output schema, the definition covers defaults (network x, suffix numbering), failure-adjacent constraints (max 25000 chars in schema), return shape ('posts with their lengths'), and the billing path including the header needed to charge prepaid credits. Nothing material an agent needs in order to call it correctly is missing.

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

Parameters4/5

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

Schema coverage is 100%, so the baseline is 3; the description earns more by giving per-network counting semantics (X weighted with links at 23, Bluesky 300 graphemes and 3000 bytes, Farcaster UTF-8 bytes with 1024 long cast, Mastodon 500, Threads emoji as UTF-8 bytes) that clarify what `network` and `limit` actually mean, and by noting numbering is counted in each post's length. It does not explain how a custom `limit` interacts with the network-specific weighting rules.

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?

States a specific verb and resource ('Split long text into a thread') plus the constraint that defines success (every post fits the network's limit, counted the way that network counts). The network list in the first sentence makes the scope concrete and separable from a simple length checker.

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 implied rather than stated: the tool is for producing a thread from long text, and 'Pure computation' signals no side effects. It never names when to prefer it over sibling length tools such as check_post_length or count_post_length, nor any when-not condition, so the agent must infer the routing.

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