Skip to main content
Glama

Xonta MAX

max_split_text

Read-onlyIdempotent

Split text into MAX messages of at most 4000 characters, cutting at paragraphs, lines or sentences.

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

Input Schema

NameRequiredDescriptionDefault
langNoAnswer language: 'en' English, 'ru' Russian. Pick the user's language; default ru (or XONTA_MAX_LANG)
textYesLong text to send
limitNoMax characters per message

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare this a read-only, idempotent, non-destructive, closed-world operation, so the safety profile is fully covered. The description usefully adds the splitting strategy (cuts at paragraphs, lines or sentences) and the hard 4000-character ceiling, but says nothing about what is returned (list of chunks, order, count) or whether any text can be lost at boundaries.

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?

A single well-formed sentence with the operation front-loaded and no filler. The phrase 'MAX messages' is slightly compressed and could be read two ways, which costs it a point.

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?

There is no output schema, so the description carries the burden of describing the return value, and it never says that a list/array of message-sized chunks comes back or how they are ordered. For a pure text-transformation tool with fully documented parameters, that missing return-shape sentence is the main gap.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so the baseline applies: text, limit and lang are each documented in the schema, including the 100-4000 range and language fallback. The description's '4000 characters' merely restates the schema default and maximum rather than adding new meaning.

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 gives a specific verb and resource ('Split text') plus the output constraint ('into MAX messages of at most 4000 characters'), so an agent can tell it converts one long string into multiple chunks. The ambiguity of 'MAX messages' (platform name vs. a maximum) and the absence of any explicit differentiation from siblings keeps it below a 5.

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: the schema labels the input 'Long text to send', which hints this is a pre-send formatting step. There is no statement of when to choose this over alternatives, no exclusion, and no mention of what to do with the resulting chunks.

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.