Skip to main content
Glama

Agent Data Tools: Full list (every tool as its own definition)

Case converter: camelCase, snake_case, kebab-case and more

case
Read-only

Convert text or identifiers between camelCase, PascalCase, snake_case, kebab-case, CONSTANT_CASE, Title Case, Sentence case, UPPER and lower. Handles mixed input like 'userID_value'. Use when renaming fields or generating code identifiers. Example: text=user profile id, to=camel. Price $0.01/call via x402 USDC or a card key (/credits), first 25 free; failed calls free. Reads or computes only and changes nothing; each call is charged, so repeats are not 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": "case"
  }
}

Input Schema

NameRequiredDescriptionDefault
toYescamel, pascal, snake, kebab, constant, title, sentence, upper or lower
textYesThe text

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior5/5

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

Annotations declare readOnlyHint/idempotentHint=false, and the description explains the non-obvious consequence: each call is billed, so repeats are not free — directly justifying the non-idempotent hint. It also discloses the pricing model ($0.01/call via x402 USDC or card key, first 25 free, failed calls free), which is decision-relevant billing/auth context an agent cannot get from annotations or schema.

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?

Purpose is front-loaded, followed by usage, an example, then cost and safety notes in a tight sequence. The closing clause ('each call is charged, so repeats are not free') partially restates the price sentence, and the pricing detail is dense, but every part is actionable.

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 two-parameter pure transform with full schema coverage and readOnly annotations, the description covers purpose, input handling, cost and side-effect profile. The only gap is that with no output schema it never states that the result is the converted string, so the return shape must be inferred.

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; the description adds real meaning on top by stating that mixed-case input like 'userID_value' is handled and by giving a concrete invocation example (text=user profile id, to=camel). It does not say whether the 'to' value is case-sensitive or accepts variants like 'camelCase' vs 'camel', which is the remaining ambiguity.

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?

"Convert text or identifiers between camelCase, PascalCase, snake_case, kebab-case, CONSTANT_CASE, Title Case, Sentence case, UPPER and lower" gives a specific verb plus an enumerated output space, so an agent knows exactly what transformation it gets. It also covers the mixed-input case ('userID_value'), which distinguishes this transform from sibling utilities like base64_encode or hash.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

"Use when renaming fields or generating code identifiers" gives a concrete usage context, and "reads or computes only and changes nothing" tells the agent it is safe to call speculatively on formatting tasks. There is no explicit when-not or named alternative, but among formatting siblings the scope is unambiguous.

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.