TextToolkit

Overview Schema Source Related Servers Discussions Admin

case_to_sentence

Convert text to Sentence case, capitalizing the first letter of each sentence. Supports optional delimiters, locale, and merging ambiguous characters.

Instructions

Convert text to Sentence case

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

Input Schema

Name	Required	Description
`text`	Yes	The text to transform to Sentence case
`delimiter`	No	The character to use between words (optional)
`locale`	No	Locale for case conversion (optional)
`mergeAmbiguousCharacters`	No	Whether to merge ambiguous characters (optional)

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Jun 21, 2026

TDQS

B3.2/5.0

Behavior2/5

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

No annotations are present. The description only says 'Convert text to Sentence case' without disclosing behavioral traits such as handling of punctuation, numbers, or special characters. For a transformation tool, more detail is needed.

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 a single sentence, very concise and to the point. No wasted words. However, it could be slightly more informative without being verbose.

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?

Given there is no output schema, the description should compensate. The 4 parameters are not explained beyond their schema descriptions. For a conversion tool, this is minimally adequate but not rich in context.

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% (all parameters have descriptions), so the baseline is 3. The tool description adds no additional meaning beyond what the schema provides, so score remains at 3.

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 description clearly states the verb 'convert' and the resource 'text' to 'Sentence case'. It distinguishes itself from sibling case conversion tools like case_to_camel, case_to_kebab, etc.

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 alternatives. The sibling tools list many case converters, but there is no indication of which one to choose or any exclusions.

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