Skip to main content
Glama

Text Analysis & Cleanup Tools (Tanod)

text_case

Read-onlyIdempotent

utilpeek: Convert text case: title, sentence, snake, camel, kebab, ... For a URL slug use make_slug. Returns the text in another case: upper, lower, title (small words such as a, of, the kept lower-case; iPhone and domains kept), sentence, camel, pascal, snake, kebab, constant, dot or alternating; identifier styles split camelCase, acronym and digit boundaries per line. Typically under 0.3 s. Price: USD 0.001. Free: 10 utilpeek calls per IP per UTC day. The submitted text is never logged or stored.

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": "text_case"
  }
}

Input Schema

NameRequiredDescriptionDefault
toYesupper, lower, title, sentence, camel, pascal, snake, kebab, constant, dot or alternating.
textYesThe text (at most 200,000 characters).

Output Schema

NameRequiredDescriptionDefault
caseNo
textNo
errorNoOnly on an error result: an object {code, message}, or the reason string of an x402 PaymentRequired object.
lengthNo
sourceNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • removedInput schema / properties / text / title
      Removed value: -"Text"
    • removedInput schema / properties / to / title
      Removed value: -"To"
    • removedInput schema / title
      Removed value: -"text_caseArguments"
  2. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "properties": {
      +    "case": {
      +      "type": [
      +        "string",
      +        "null"
      +      ]
      +    },
      +    "error": {
      +      "description": "Only on an error result: an object {code, message}, or the reason string of an x402 PaymentRequired object."
      +    },
      +    "length": {
      +      "type": [
      +        "integer",
      +        "null"
      +      ]
      +    },
      +    "source": {
      +      "type": [
      +        "object",
      +        "null"
      +      ]
      +    },
      +    "text": {
      +      "type": [
      +        "string",
      +        "null"
      +      ]
      +    }
      +  },
      +  "type": "object"
      +}
  3. First observed

TDQS

A4.5/5.0
Behavior5/5

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

Annotations already declare readOnly, idempotent, non-destructive, closed-world behavior, and the description adds substantial context beyond them: sub-0.3s latency, price of USD 0.001, a free tier of 10 calls per IP per UTC day, and an explicit privacy guarantee that submitted text is never logged or stored. It also discloses non-obvious semantics such as title case keeping small words lower-case and preserving iPhone/domain casing, and that identifier styles split camelCase, acronym and digit boundaries.

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?

The purpose and target list are front-loaded, and the pricing/rate-limit/privacy notes are useful rather than filler. It is dense and slightly repetitive (the case list appears again in the return-value sentence, and the first list trails off with "..."), which costs a point but does not obscure the core meaning.

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 read-only transform with a 100% documented schema and an output schema, the description covers purpose, the one relevant alternative, cost, limits and privacy. The only residual gaps are edge-case behavior (invalid or exotic unicode input, whether whitespace is normalized), which are not essential to calling it correctly.

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 schema already documents both parameters and the enum. The description still adds meaning beyond the enum listing by explaining what "title" actually does (small words kept lower-case, iPhone and domains preserved) and how identifier-style conversions handle boundaries, which an agent could not infer from the raw enum values.

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?

The description opens with a specific verb+resource ("Convert text case") and immediately enumerates the supported target cases, then explicitly distinguishes itself from the sibling make_slug. An agent can tell exactly what this tool does and what it does not do without opening the 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?

It gives a concrete routing rule: "For a URL slug use make_slug." That covers the most likely ambiguity among siblings. It does not state exclusions for the other case-related tools (e.g. text_replace or text_encode), but the scope here is narrow enough that this is a minor gap.

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.