Skip to main content
Glama

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

String utilities: every case, slug, counts and more

pack_string_toolbox
Read-only

Transform one string every common way at once: camelCase, PascalCase, snake_case, kebab-case, CONSTANT_CASE, dot.case, path/case, Title Case, Sentence case, upper and lower; a URL slug (accents removed); reversed; trimmed and whitespace-collapsed; and counts of characters, letters, digits, words and lines. Splits identifiers like userIDValue or XMLHttpRequest correctly. Use when naming fields, files and routes or cleaning user input. Example: text=Hello World, user profile ID 42. 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>"
    },
    "name": "pack_string_toolbox"
  }
}

Input Schema

NameRequiredDescriptionDefault
textYesThe string (up to 10,000 characters)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior5/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false and idempotentHint=false; the description adds real context beyond them: it explains why repeats are not free ("each call is charged"), discloses pricing and a free tier (first 25 free, failed calls free), states the reads/computes-only behavior explicitly, and notes that accents are stripped in the slug and that identifiers like userIDValue/XMLHttpRequest split correctly. That is meaningful behavioral and cost disclosure an agent could not get from the annotations.

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?

Front-loaded with the list of transformations, then splitting behavior, usage context, an example, and pricing/safety. Dense but each clause carries information; the pricing sentence is long and jargon-heavy (x402 USDC, /credits) but is genuinely useful cost context rather than filler.

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 one-parameter read-only computation tool with no output schema, the description covers inputs, limits (via schema), cost, and side-effect-free behavior. The remaining gap is the shape of the return value: it lists what is computed but never says whether results come back as a flat object of named cases plus a counts object, which matters since no output schema exists.

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?

There is a single parameter with 100% schema description coverage, which already states it is a string up to 10,000 characters. The description adds only an illustrative example ("text=Hello World, user profile ID 42") that shows arbitrary mixed content is accepted, but gives no additional format or boundary semantics beyond the schema baseline.

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?

States a specific verb ("Transform one string") and enumerates the exact resources produced: camelCase, PascalCase, snake_case, kebab-case, CONSTANT_CASE, dot.case, path/case, Title Case, Sentence case, slug, reversed, trimmed, plus counts. The phrase "every common way at once" distinguishes it from the single-purpose siblings (case, slug), so an agent can tell why it would pick this tool over those without opening a schema.

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 naming fields, files and routes or cleaning user input" gives concrete usage contexts, and the example shows a realistic mixed input. It stops short of explicit exclusions or naming the alternative single-case tools, so an agent must infer that case/slug are the narrower choices rather than being told.

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.