Skip to main content
Glama

TinyFn

by io.tinyfn

title_case

Convert text to title case.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
textYesThe text to title case

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
originalYes
title_caseYes

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Changed3 schema fields changed
    • addedOutput schema / $defs / TitleCaseResponse
      Added value: +{
+  "properties": {
+    "original": {
+      "title": "Original",
+      "type": "string"
+    },
+    "title_case": {
+      "title": "Title Case",
+      "type": "string"
+    }
+  },
+  "required": [
+    "original",
+    "title_case"
+  ],
+  "title": "TitleCaseResponse",
+  "type": "object"
+}
    • removedOutput schema / $defs / app__routers__string_utils__TitleCaseResponse
      Removed value: -{
-  "properties": {
-    "original": {
-      "title": "Original",
-      "type": "string"
-    },
-    "title_case": {
-      "title": "Title Case",
-      "type": "string"
-    }
-  },
-  "required": [
-    "original",
-    "title_case"
-  ],
-  "title": "TitleCaseResponse",
-  "type": "object"
-}
    • changedOutput schema / x-fastmcp-top-level-schema
      Previous value: -"app__routers__string_utils__TitleCaseResponse"New value: +"TitleCaseResponse"
  2. Changed3 schema fields changed
    • removedOutput schema / $defs / TitleCaseResponse
      Removed value: -{
-  "properties": {
-    "original": {
-      "title": "Original",
-      "type": "string"
-    },
-    "title_case": {
-      "title": "Title Case",
-      "type": "string"
-    }
-  },
-  "required": [
-    "original",
-    "title_case"
-  ],
-  "title": "TitleCaseResponse",
-  "type": "object"
-}
    • addedOutput schema / $defs / app__routers__string_utils__TitleCaseResponse
      Added value: +{
+  "properties": {
+    "original": {
+      "title": "Original",
+      "type": "string"
+    },
+    "title_case": {
+      "title": "Title Case",
+      "type": "string"
+    }
+  },
+  "required": [
+    "original",
+    "title_case"
+  ],
+  "title": "TitleCaseResponse",
+  "type": "object"
+}
    • changedOutput schema / x-fastmcp-top-level-schema
      Previous value: -"TitleCaseResponse"New value: +"app__routers__string_utils__TitleCaseResponse"
  3. Changed3 schema fields changed
    • addedOutput schema / $defs / TitleCaseResponse
      Added value: +{
+  "properties": {
+    "original": {
+      "title": "Original",
+      "type": "string"
+    },
+    "title_case": {
+      "title": "Title Case",
+      "type": "string"
+    }
+  },
+  "required": [
+    "original",
+    "title_case"
+  ],
+  "title": "TitleCaseResponse",
+  "type": "object"
+}
    • removedOutput schema / $defs / app__routers__string_utils__TitleCaseResponse
      Removed value: -{
-  "properties": {
-    "original": {
-      "title": "Original",
-      "type": "string"
-    },
-    "title_case": {
-      "title": "Title Case",
-      "type": "string"
-    }
-  },
-  "required": [
-    "original",
-    "title_case"
-  ],
-  "title": "TitleCaseResponse",
-  "type": "object"
-}
    • changedOutput schema / x-fastmcp-top-level-schema
      Previous value: -"app__routers__string_utils__TitleCaseResponse"New value: +"TitleCaseResponse"
  4. Changed3 schema fields changed
    • removedOutput schema / $defs / TitleCaseResponse
      Removed value: -{
-  "properties": {
-    "original": {
-      "title": "Original",
-      "type": "string"
-    },
-    "title_case": {
-      "title": "Title Case",
-      "type": "string"
-    }
-  },
-  "required": [
-    "original",
-    "title_case"
-  ],
-  "title": "TitleCaseResponse",
-  "type": "object"
-}
    • addedOutput schema / $defs / app__routers__string_utils__TitleCaseResponse
      Added value: +{
+  "properties": {
+    "original": {
+      "title": "Original",
+      "type": "string"
+    },
+    "title_case": {
+      "title": "Title Case",
+      "type": "string"
+    }
+  },
+  "required": [
+    "original",
+    "title_case"
+  ],
+  "title": "TitleCaseResponse",
+  "type": "object"
+}
    • changedOutput schema / x-fastmcp-top-level-schema
      Previous value: -"TitleCaseResponse"New value: +"app__routers__string_utils__TitleCaseResponse"
  5. Changed3 schema fields changed
    • addedOutput schema / $defs / TitleCaseResponse
      Added value: +{
+  "properties": {
+    "original": {
+      "title": "Original",
+      "type": "string"
+    },
+    "title_case": {
+      "title": "Title Case",
+      "type": "string"
+    }
+  },
+  "required": [
+    "original",
+    "title_case"
+  ],
+  "title": "TitleCaseResponse",
+  "type": "object"
+}
    • removedOutput schema / $defs / app__routers__string_utils__TitleCaseResponse
      Removed value: -{
-  "properties": {
-    "original": {
-      "title": "Original",
-      "type": "string"
-    },
-    "title_case": {
-      "title": "Title Case",
-      "type": "string"
-    }
-  },
-  "required": [
-    "original",
-    "title_case"
-  ],
-  "title": "TitleCaseResponse",
-  "type": "object"
-}
    • changedOutput schema / x-fastmcp-top-level-schema
      Previous value: -"app__routers__string_utils__TitleCaseResponse"New value: +"TitleCaseResponse"
  6. First observed

TDQS

C2.9/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It only restates the high-level operation without clarifying which title-case convention is used, how acronyms or prepositions are handled, or whether special characters and whitespace are preserved.

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 description is a single, front-loaded sentence with no redundant phrasing or filler. It is appropriately concise for a simple transformation, though it sacrifices useful differentiating context for brevity.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The transformation is simple, the schema covers the parameter, and an output schema exists, so the description is minimally sufficient for the basic call. However, given the large number of similar case-conversion siblings, it lacks the guidance needed to confidently select this tool in context.

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?

The schema fully describes the only parameter ('The text to title case'), and the description adds no additional semantic detail beyond the schema. This matches the baseline for full schema coverage.

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 clearly states a specific action ('Convert') on a specific resource ('text') with a clear target outcome ('title case'). However, it does not differentiate this tool from closely related siblings like smart_title_case or to_title_case.

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?

There is no guidance on when to use this tool versus alternatives. With a large set of sibling case-conversion tools, the absence of any exclusions or preferred usage conditions leaves the agent to infer the correct choice.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All TinyFn toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

C2.3/5.0
Disambiguation2/5

Many tools have overlapping purposes, such as multiple random generators (random_integer, random_number), duplicate hashing functions (hash_md5, md5_checksum), and near-identical tools (compare, compare_2, compare_decimals). The sheer number of tools and lack of clear boundaries make it difficult for an agent to differentiate.

Naming Consistency1/5

Naming is highly inconsistent. There are duplicate tools with different names (camel_case vs to_camel_case, slug vs slugify), arbitrary suffixes like '_2', and mixing of patterns (e.g., generate_password vs password_entropy). No clear convention is followed.

Tool Count1/5

With 572 tools, the server is massively overpopulated for any coherent purpose. It includes trivial endpoints (true_endpoint, null, hello_world) and numerous duplicates, far exceeding a well-scoped utility set.

Completeness2/5

While the server covers many domains (math, strings, dates, colors, etc.), the presence of duplicate and trivial tools indicates a lack of thoughtful curation. There are gaps in basic operations (e.g., no dedicated file or network tools), and many tools are redundant.

Resources