Skip to main content
Glama

camelsnake_convert

Read-onlyIdempotent

Convert identifiers between camelCase, PascalCase, snake_case, kebab-case, and CONSTANT_CASE by specifying source text and an optional target case.

Instructions

Convert between camelCase, PascalCase, snake_case, kebab-case, and CONSTANT_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": "camelsnake_convert"
  }
}

Input Schema

NameRequiredDescriptionDefault
textYesIdentifier or text to convert.
targetNoTarget case: camel, pascal, snake, kebab, constant. Omit for all.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.1.11

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, openWorldHint=true, and destructiveHint=false, so the safety profile is covered. The description adds only the list of supported case formats, without disclosing conversion behavior such as acronym handling, ambiguous input behavior, or what happens when target is omitted.

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 a single well-formed sentence, front-loaded with the core action and the supported formats. There is no wasted text.

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 pure conversion tool, the description plus schema is largely sufficient. It does not describe the return shape, especially when target is omitted and multiple formats are returned, but no output schema exists and the core operation is clear.

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 both parameters are already documented in the schema, including the target case options and the 'omit for all' behavior. The description adds no parameter semantics beyond what the schema provides.

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 gives a clear verb and specific resource: convert between named case formats. It does not explicitly distinguish this from sibling tools like string_case or text_slugify, but the supported case list makes the purpose concrete.

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 states what the tool does but gives no guidance on when to use it versus alternatives. It does not mention relevant sibling tools or any exclusion cases.

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