API Hub MCP — 337+ Tools

truncate_text

Truncate text to a specified maximum length with an optional ellipsis. Control exact character count and append '...' as needed.

Instructions

Truncate text to specified length with optional ellipsis.

Parameters:
    text — Text to truncate.
    length — Maximum length (default: 100).
    ellipsis — Append '...' (default: true).

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

Input Schema

Name	Required	Description	Default
`text`	Yes
`length`	No
`ellipsis`	No

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv2.4.1Jun 22, 2026

TDQS

B3.2/5.0

Behavior3/5

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

The description explains the core behavior: truncation with optional ellipsis and default length. However, it does not disclose edge cases (e.g., text shorter than length) or any side effects. Without annotations, this is adequate but not comprehensive.

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?

The description is concise: one sentence stating the purpose followed by a parameter list. It is front-loaded and avoids redundancy, earning its place efficiently.

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?

The description covers the main functionality but does not mention return value. Since an output schema exists (as per context), the description does not need to explain return values, but it could still hint at what to expect.

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?

With 0% schema description coverage, the description adds meaning by listing parameters with brief explanations ('text — Text to truncate.'). This compensates for the schema gap but is minimal and does not elaborate on parameter constraints.

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 clearly states the verb 'Truncate' and the resource 'text', specifying the behavior with length and ellipsis options. It distinguishes itself from sibling text manipulation tools like 'capitalize_text' or 'reverse_text' by its specific truncation function.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No guidance is provided on when to use this tool versus other text tools. There is no mention of when not to use it or context like typical use cases.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server