Skip to main content
Glama

jimu (renamed to Tax Compass)

X(旧 Twitter)の投稿の文字数(日本語は140字)

x_post_weighted_length
Read-onlyIdempotent

Count the length of a post on X (formerly Twitter) exactly as X does, using X's official twitter-text library: weighted characters where CJK (Japanese, Chinese, Korean) and emoji count 2, most Latin characters count 1, every URL counts 23, text is NFC-normalized, and the limit is 280 (about 140 Japanese characters). It is meant for checking X posts, especially Japanese ones, against the limit. is_valid is also false for an empty text or text with characters X does not accept. Counts only the text given (auto-added reply @mentions and attached media are not counted by X). Long posts for paid accounts are not covered; the text may be at most 1,000 UTF-16 code units, also after NFC normalization. The text is not stored or returned.

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

Input Schema

NameRequiredDescriptionDefault
textYes数える本文(UTF-16 で 1,000 まで。NFC にした後も 1,000 まで)

Output Schema

NameRequiredDescriptionDefault
notesYesこの答えに効いた決まり・前提(日本語)
resultYes
doc_urlYes人が読む説明のページ(式・出所・例)。利用者に次に読んでもらう先
sourcesYes
law_as_ofNo出所が書く法令の基準日(例:2026-04-01=令和8年4月1日現在法令等)
checked_onYesCyclix Agents が出所を最後に確かめた日
disclaimerYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive and a closed-world operation, so the safety profile is covered. The description nonetheless adds real value beyond them: what is excluded from the count, that is_valid is false for empty or X-rejected characters, and the 1,000 UTF-16 code unit cap before and after NFC. It never describes the return payload shape, but an output schema exists to carry that.

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?

Purpose and the counting algorithm are front-loaded before the caveats, and every clause carries information (weights, normalization, limits, exclusions). The sentences run long and pack several distinct facts per sentence, which costs a little scannability but wastes no content.

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 single-parameter utility with a full schema and an output schema, the description covers everything an agent needs: semantics, limits, normalization, exclusions, and what is not covered. Return values are rightly left to the output schema.

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% and the single parameter's schema already documents the 1,000 UTF-16 cap after NFC, so the baseline would be 3. The description earns an extra point by explaining that only the supplied text is counted and that the text is neither stored nor returned, which is behavior an agent needs when passing user content.

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 precise verb and resource ('Count the length of a post on X') and immediately pins down the algorithm: X's official twitter-text, weighted characters, CJK/emoji = 2, URL = 23, limit 280 / ~140 Japanese characters. An agent knows exactly what this computes and cannot confuse it with any sibling.

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?

Explicitly scopes usage ('meant for checking X posts, especially Japanese ones, against the limit') and names exclusions: auto-added reply @mentions and attached media are not counted, and long posts for paid accounts are out of scope. It stops short of stating when to prefer some other tool, but no plausible alternative exists among the listed siblings.

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