Skip to main content
Glama

Case Converter API - UPPER, lower, Title, camelCase, snake_case, kebab-case

case_converter
Read-onlyIdempotent

Convert text to upper, lower, title, sentence, camel, snake or kebab case. Runs on our server, files are deleted right after the call, nothing stored. Free: 25 calls/day per IP. Paid: $0.001 per call via x402 at https://radarbg.com/x402/case-converter.

Example tool call

This call uses example arguments supplied in the tool’s input schema.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "to": "camel",
      "text": "hello big world"
    },
    "name": "case_converter"
  }
}

Input Schema

NameRequiredDescriptionDefault
toNoTarget casetitle
textYesThe text

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?

Annotations already declare readOnlyHint, openWorldHint, and idempotentHint, and the description adds substantive behavior beyond them: server-side execution, immediate file deletion, no storage, a per-IP daily quota, and a paid x402 endpoint with price. The mention of 'files' is slightly incongruous for a text-only schema, but it does not contradict any annotation.

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

Conciseness5/5

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

Three short sentences, front-loaded with the capability and followed by privacy, quota, and pricing facts. Every sentence carries information an agent or caller would need, with no filler.

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

Completeness5/5

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

For a two-parameter, single-purpose text transformation with full schema coverage, existing annotations, and no output schema, the description covers purpose, privacy, rate limits, and paid access. Nothing essential to correct invocation is missing.

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%, with both 'text' and 'to' documented and the enum fully enumerated in the schema. The description restates the case options but adds no syntax, default-value, or edge-case meaning beyond the schema, so the baseline of 3 applies.

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 opens with a specific verb ('Convert') and resource ('text') and enumerates every supported target case (upper, lower, title, sentence, camel, snake, kebab), so an agent knows exactly what the tool produces. It is clearly distinguishable from sibling converters such as time_zone_converter or unit_converter.

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 implied by the enumeration of cases, and the description supplies operational context (free tier of 25 calls/day per IP, paid x402 route), but it never states when to prefer this tool over an alternative or any preconditions beyond pricing. No explicit when-not guidance is given.

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