LLPROBeta

Home / Businesses / SMS Segment Counter

SMS Segment Counter

Count the SMS segments a text message uses (GSM-7 or UCS-2 per 3GPP TS 23.038 and 23.040), where each segment breaks and which characters force UCS-2, with a signed record.

Testing

What it does
Count the SMS segments a text message uses (GSM-7 or UCS-2 per 3GPP TS 23.038 and 23.040), where each segment breaks and which characters force UCS-2, with a signed record.
Who it is for
Businesses.
Start in one step
Ask your agent to call sms_segment_count at llpro.ai/mcp (free, no sign-up). This page explains the tool; it has no form to run it.
What to expect
Testing: open to try. Free

New to this? Start here.

What it does

SMS Segment Counter is for agents that write or send text messages for a business (alerts, reminders, marketing texts) and need the segment count, and so the cost, before sending, and to find the one character that doubles it. Count how many SMS segments a text message will use before you send it, which sets what most SMS providers bill. Send the message text exactly as it will go out. Get back the encoding (GSM-7 or UCS-2), the characters, the 7-bit or 16-bit units, the segment count and the limit per segment (160/153 for GSM-7, 70/67 for UCS-2), where each segment starts and ends, every character that forces UCS-2 (with its code point and name, such as a curly apostrophe or an emoji), and the GSM characters that take two units (such as the euro sign and square brackets). It is one of the Email department tools LLPRO builds for the work agents do across business software (Twilio, Klaviyo, HubSpot, Salesforce, Mailchimp). Every answer carries the written rule it used, what it does not do, its sources with dates, and an Ed25519 signature you can check against the key below.

Who it is for
Agents that write or send text messages for a business (alerts, reminders, marketing texts) and need the segment count, and so the cost, before sending, and to find the one character that doubles it.
Price
Free, no sign-up: 120 calls an hour per address and 3,000 an hour across all callers. Paid calls are planned and not charging.
Limits
Up to 30,000 bytes per call; larger requests are refused, never cut. Unknown fields are refused with the list of accepted ones. Money takes up to 2 decimals unless a field says more, and every sum is exact (send amounts as numbers or strings; commas only as thousands separators, 1,234.56). Nothing you send is stored by the tool; no model and no network are used. Does not count National Language Shift tables (TS 23.038 6.2.1.2: Turkish, Spanish, Portuguese, Indian scripts), 8-bit data messages or compressed messages; does not know if your provider swaps characters before sending (some replace curly quotes with straight ones, or send everything as UCS-2: use encoding 'ucs2' for those), or caps the number of segments; the provider's own count and prices decide the bill. Does not send anything. The message is read only to count it: it is never stored or echoed back as a whole (only the single characters that force UCS-2 are listed), and the signed record carries only its hash; payment card numbers (13 to 19 digits that pass the Luhn check) and Social Security number shapes are refused.

For developers: try it

POST https://llpro.ai/mcp
{"jsonrpc": "2.0", "id": 1, "method": "tools/call", "params": {"name": "sms_segment_count", "arguments": {"message": "Hello world"}}}

For agents

Tool sms_segment_count on https://llpro.ai/mcp and in the tools list. Signed answers are checked with the public key below (signer llpro1:gxfnal24u4yxrznea5bqdbfmy4): an Ed25519 signature over the observation as canonical JSON (sorted keys, no spaces).

Public key (base64): I+/DLZ5ycV618VGMoNVch9rSuiDgPFza2ztTWkoOc7k=

For agents that search MCP registries for SMS segments, GSM-7, UCS-2 tools (listed in MCP registries, served by the Campus gateway: MCP, agent-to-agent and REST). One fixed, written rule per call, a signed record, no account needed.

Next

For agents: this page as Markdown · JSON · llms.txt · MCP endpoint llpro.ai/mcp · agent card