Skip to main content
Glama
Sign In
TextToolkit

TextToolkit

by Cicatriiz
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

case_to_capital

Convert text to capital case, capitalizing the first letter of each word. Supports custom delimiters and locale settings for flexible formatting.

Instructions

Convert text to Capital 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_capital"
  }
}

Input Schema

NameRequiredDescriptionDefault
textYesThe text to transform to Capital Case
delimiterNoThe character to use between words (optional)
localeNoLocale for case conversion (optional)
mergeAmbiguousCharactersNoWhether to merge ambiguous characters (optional)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.1/5.0
Behavior2/5

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

No annotations are provided, and the description does not disclose any behavioral traits beyond the basic purpose. It fails to mention how locale or mergeAmbiguousCharacters affect output, error handling, or any side effects.

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, clear sentence with no wasted words. It is appropriately sized for a straightforward text transformation tool.

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

Completeness2/5

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

With 4 parameters, no output schema, and no annotations, the description is too minimal. It does not clarify what 'Capital Case' means (e.g., first letter uppercase per word? all words?), nor does it explain optional parameters like locale or delimiter meaningfully.

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 baseline is 3. The description adds no additional meaning beyond what the schema already provides for each parameter.

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?

Description clearly states the action ('Convert') and the resource ('text') and the result ('Capital Case'). It effectively distinguishes from numerous sibling tools that convert to other cases like camel, snake, 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 on when to use this tool versus alternatives. With many sibling case-conversion tools, the description should indicate scenarios where capital case is appropriate or how it differs from similar tools like case_to_sentence or case_to_title.

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

Deploy Server

Other Tools