Skip to main content
Glama

WritersLogic business agents

platform-text-fit

Does this text fit: SMS segments, X posts, store listings, ad and push limits — Checks up to 50 texts per call against a platform limit, for an agent writing a message, post, store listing, ad or push payload that must not be truncated or split. sms: GSM 7 bit vs UCS-2 and the exact segment boundaries per 3GPP TS 23.038 (extension characters cost 2 septets and never straddle a segment; an emoji is 2 UTF-16 units). x: weighted length per the open-source twitter-text config v3

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": {
      "items": "<items>"
    },
    "name": "platform-text-fit"
  }
}

Input Schema

NameRequiredDescriptionDefault
itemsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does substantial work: it discloses the 50-text per-call cap, GSM 7-bit vs UCS-2 handling, the rule that extension characters cost 2 septets and never straddle a segment, that an emoji is 2 UTF-16 units, and that X uses weighted length per twitter-text config v3. It does not describe the response shape, so the caller cannot tell whether it gets a boolean, a segment count, or remaining characters.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The core purpose is front-loaded and there is little filler, but the tail is a run-on fragment ('sms: ... x: ...') that trails off with an unterminated quotation and trailing space, suggesting truncation. The density is earned, yet the packaging makes the platform rules harder to scan than they need to be.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a validation tool with nested item objects and no output schema, the description covers input-side rules well but never explains what a check returns — fit status, remaining characters, segment count, or per-platform reasons. That omission is the main gap an agent would hit after the call.

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?

The schema documents the parameters, but the description adds real semantic depth for the platform values: sms is tied to GSM 7-bit/UCS-2 segment boundaries under 3GPP TS 23.038 and x to weighted length under the twitter-text v3 config. It leaves the app-store, google-play, google-ads, apns and fcm modes without equivalent rule detail, relying on the schema's field enumerations for those.

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 opening clause names a specific check ('Does this text fit') against named limits (SMS segments, X posts, store listings, ad and push limits), and the second clause states the operation precisely: check up to 50 texts per call against a platform limit. An agent can distinguish this from siblings such as text-offsets or redact-text without opening the schema.

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?

It gives a clear use context — 'for an agent writing a message, post, store listing, ad or push payload that must not be truncated or split' — telling the caller when the tool applies. It stops short of naming when-not-to-use conditions or pointing at an alternative tool for related tasks, so it is clear but not exhaustive.

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