Skip to main content
Glama

Korea SMS Length & Ad Rules Check

Check a Korean advertising text message

kr_ad_sms_check
Read-onlyIdempotent

Check a Korean marketing text message against the display rules of the Network Act Art. 50 and Enforcement Decree Annex 6, and the night-time (21:00-08:00 KST) separate-consent rule when send_at is given. Returns each check with the legal basis.

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_ad_sms_check"
  }
}

Input Schema

NameRequiredDescriptionDefault
textYes
send_atNoKorea time HH:MM

Output Schema

NameRequiredDescriptionDefault
passedYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, openWorldHint=false and idempotentHint, so safety is covered. The description adds genuine behavioral context beyond them: the conditional night-time rule (21:00-08:00 KST) triggered by send_at, and that results are returned per-check with their legal basis.

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?

One front-loaded sentence with no filler; the verb and scope come first. It is dense with legal citations, which slightly raises parsing effort, but nothing is redundant.

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 two-parameter read-only check with an output schema and full annotation coverage, the description supplies the legal basis, the conditional rule, and what the response contains. Remaining minor gaps (e.g., how text length or non-Korean input is handled) are not essential to calling 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 50% – send_at is documented as 'Korea time HH:MM' but text is undocumented. The description compensates by establishing that text must be a Korean marketing message and that send_at is what activates the night-time consent evaluation, adding meaning the schema does not carry.

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 (Check) and a specific resource (a Korean marketing/advertising text message) against named legal standards (Network Act Art. 50, Enforcement Decree Annex 6). This clearly separates it from the sibling kr_sms_length, which by name alone concerns length measurement rather than legal compliance.

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?

Gives clear context for use: verifying display-rule compliance, with the night-time separate-consent check activated only 'when send_at is given'. It does not name when-not conditions or explicitly route to kr_sms_length for length checks, so it stops short of full alternative guidance.

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