GadgetHumans API Hub

case_convert

Convert text between upper, lower, title, sentence, camel, snake and kebab case. Pure CPU, instant.

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_convert"
  }
}

Input Schema

Name	Required	Description	Default
`to`	No	Target case
`text`	Yes	Text to convert

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 8, 2026
RemovedNov 6, 2026

Changed3 schema fields changedNov 3, 2026

addedInput schema / properties / text

Added value: +{
+  "description": "Text to convert",
+  "type": "string"
+}

addedInput schema / properties / to

Added value: +{
+  "description": "Target case",
+  "type": "string"
+}

addedInput schema / required
```
Added value: +[
+  "text"
+]
```

AddedNov 2, 2026

TDQS

A3.5/5.0

Behavior3/5

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

With no annotations, the description carries the full behavioral burden. 'Pure CPU, instant' usefully signals no external calls and fast execution, but it omits behavior for unsupported target cases or missing optional parameters.

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?

The description is two short sentences with the main purpose front-loaded. 'Pure CPU, instant' adds useful context without wasting words.

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

Completeness4/5

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

For a simple two-parameter conversion tool with full schema coverage and no output schema, the description is mostly complete. The remaining gap is the optional 'to' parameter's default behavior, which is not stated.

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

Parameters4/5

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

Schema coverage is 100%, so the baseline is 3, but the description adds real value by enumerating valid case values even though the schema has no enum for 'to'. It does not clarify the default when the optional 'to' parameter is omitted.

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 uses a specific verb, 'Convert', and a clear resource, 'text', then enumerates seven target cases. It does not distinguish this tool from the sibling title_case, which overlaps directly.

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?

The description implies general text-case conversion but gives no explicit when-to-use guidance, exclusions, or comparison to the sibling title_case. An agent must infer selection criteria entirely.

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

All GadgetHumans API Hub tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.