Skip to main content
Glama

Korea SMS Length & Ad Rules Check

Korean SMS/LMS byte count

kr_sms_length
Read-onlyIdempotent

Count message bytes as Korean carriers do (Korean/CJK 2 bytes, ASCII 1) and tell whether it fits SMS (90 bytes) or LMS (2,000 bytes). Flags emoji and other characters that may break in SMS.

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": "kr_sms_length"
  }
}

Input Schema

NameRequiredDescriptionDefault
textYes

Output Schema

NameRequiredDescriptionDefault
typeYes
bytesYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already establish that this is a pure, idempotent read with no external side effects, so the bar is lower. The description then adds genuine behavioral detail not in structured fields: the 2-byte/1-byte counting rule, the concrete 90/2,000-byte thresholds, and the fact that emoji or unusual characters are flagged as potentially breaking. It stops short of explaining how flagged characters are reported, which the output schema presumably covers.

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?

Two tight sentences with no filler. The counting method and thresholds are front-loaded, and the edge-case warning follows logically, so every clause earns its place.

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 single-parameter calculation tool with an output schema covering the return values and annotations covering safety, the description supplies the domain rules (byte weights, SMS/LMS cutoffs, emoji risk) an agent needs to interpret results. What remains missing is any steering relative to the sibling tool, a minor gap given the tool's low complexity.

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 0%, but there is a single required parameter whose meaning ('the message text to measure') is fully implied by 'Count message bytes'. The description also explains what the tool does with that input, effectively compensating for the bare schema, though it does not mention the 5,000-character cap or any input normalization behavior.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific verb ('count') and resource ('message bytes') and specifies the exact counting convention used by Korean carriers. It does not name or differentiate against the sibling kr_ad_sms_check, so it falls short of a 5, but the purpose itself is unambiguous.

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 only implied: an agent can infer this is a pre-send validation check because it reports SMS/LMS fitting thresholds. There is no explicit 'use this when...' statement and no guidance on how it relates to the sibling compliance-check tool, leaving the agent to infer the boundary.

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