Skip to main content
Glama

Convert text case

bursia_case_convert
Read-onlyIdempotent

Convert text to camelCase, snake_case, kebab-case, PascalCase, UPPER or lower. Pure computation, free.

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>",
      "to": "<to>"
    },
    "name": "bursia_case_convert"
  }
}

Input Schema

NameRequiredDescriptionDefault
toYesTarget case.
textYesThe text to convert, e.g. "user account id".

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • addedInput schema / properties / text / description
      Added value: +"The text to convert, e.g. \"user account id\"."
    • addedInput schema / properties / to / description
      Added value: +"Target case."
    • addedInput schema / properties / to / enum
      Added value: +[
      +  "camel",
      +  "snake",
      +  "kebab",
      +  "pascal",
      +  "upper",
      +  "lower"
      +]
  2. First observed

TDQS

A3.7/5.0
Behavior3/5

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

The annotations already declare readOnlyHint, idempotentHint, destructiveHint=false, and openWorldHint=false, so the safety profile is well covered. The description adds that the operation is 'Pure computation, free,' which usefully clarifies that there is no side effect or cost, but it does not describe edge-case behavior such as acronym handling or invalid input handling.

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 compact sentences, front-loaded with the operation and the supported formats. Every phrase contributes to the agent's understanding, with no redundant or filler content.

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, pure-computation conversion tool with full schema coverage and rich annotations, the description provides sufficient context to call it correctly. No output schema exists, but the tool's simple return behavior does not require additional explanation in the description.

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 coverage is 100%, and both parameters are documented directly in the schema, including an enum for the 'to' parameter and an example for 'text'. The description merely repeats the enum values in prose, so it does not add meaning beyond what the schema already 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 names a specific verb (Convert) and resource (text) and enumerates the supported target formats, which lets an agent understand the operation without opening the schema. It does not explicitly differentiate this tool from the similarly named sibling bursia_slugify, which also transforms text.

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?

The use case is strongly implied by the description: transform a string into one of the listed cases. However, it offers no explicit when-to-use or when-not-to-use guidance, and it does not name alternatives such as bursia_slugify, leaving the agent to infer which text-transform tool is appropriate.

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