Skip to main content
Glama

Thread Kit: posts that fit every network

Check one post and get a version that fits ($0.001)

check_post_length
Read-onlyIdempotent

Full check of one post for a network: valid or not, exact length in that network's unit, remaining, issues (over the limit, byte cap, too many links, invalid characters, NFC) and a "fitted" version cut at a sentence or word boundary with an ellipsis when it is too long. 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. For the length alone use the free count_post_length. PAID: $0.001 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": "check_post_length"
  }
}

Input Schema

NameRequiredDescriptionDefault
textYesThe post text (any language)
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)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.8/5.0
Behavior5/5

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

Annotations already declare readOnly, idempotent, non-destructive, and closed-world, so the safety profile is covered. The description adds genuinely new behavioral context beyond that: the $0.001 USDC-on-Base x402 charge and the option to draw from prepaid credits with a Bearer token, which an agent must know before invoking a paid tool.

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?

The core purpose and outputs are front-loaded, and each network clause carries distinct information. It is dense and the payment sentence plus network enumeration make it long, but almost no sentence is filler; slight trimming of repeated per-network limits would tighten it.

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 three-parameter paid check tool with no output schema, the description still explains the return payload (validity, length, remaining, issues, fitted version) and the counting semantics per network. Combined with annotations and full schema coverage, an agent has everything needed to call it correctly.

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, but the description goes further by documenting the per-network counting rules behind `limit` and `network`: X weighted counts with links fixed at 23 and a 280 limit, Bluesky 300 graphemes and 3000 bytes, Farcaster 320/1024 UTF-8 bytes, Mastodon 500, Threads 500 with emoji byte counting. That adds real meaning to the enum values beyond the schema text.

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 opens with a specific verb and resource ('Full check of one post for a network') and enumerates the concrete outputs: validity, exact length, remaining, issues, and a 'fitted' version cut at a boundary. It clearly separates itself from the sibling count_post_length by promising issue detection and a corrected post rather than a bare count.

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

Usage Guidelines5/5

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

It explicitly routes the agent: 'For the length alone use the free count_post_length,' giving both the alternative and the condition that selects it. It also states the paid path and the credit alternative via the Authorization header, so the agent knows prerequisites before calling.

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