Skip to main content
Glama

TinyFn

by io.tinyfn

smart_title_case

Smart title case (handles articles, prepositions).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
textYesText to convert

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
originalYesOriginal input text
title_caseYesText converted to smart title case (articles/prepositions lowercased)

Schema Changelog

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

  1. Changed3 schema fields changed
    • removedOutput schema / $defs / TitleCaseResponse
      Removed value: -{
-  "properties": {
-    "original": {
-      "description": "Original input text",
-      "title": "Original",
-      "type": "string"
-    },
-    "title_case": {
-      "description": "Text converted to smart title case (articles/prepositions lowercased)",
-      "title": "Title Case",
-      "type": "string"
-    }
-  },
-  "required": [
-    "original",
-    "title_case"
-  ],
-  "title": "TitleCaseResponse",
-  "type": "object"
-}
    • addedOutput schema / $defs / app__routers__text_utils__TitleCaseResponse
      Added value: +{
+  "properties": {
+    "original": {
+      "description": "Original input text",
+      "title": "Original",
+      "type": "string"
+    },
+    "title_case": {
+      "description": "Text converted to smart title case (articles/prepositions lowercased)",
+      "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__text_utils__TitleCaseResponse"
  2. Changed3 schema fields changed
    • addedOutput schema / $defs / TitleCaseResponse
      Added value: +{
+  "properties": {
+    "original": {
+      "description": "Original input text",
+      "title": "Original",
+      "type": "string"
+    },
+    "title_case": {
+      "description": "Text converted to smart title case (articles/prepositions lowercased)",
+      "title": "Title Case",
+      "type": "string"
+    }
+  },
+  "required": [
+    "original",
+    "title_case"
+  ],
+  "title": "TitleCaseResponse",
+  "type": "object"
+}
    • removedOutput schema / $defs / app__routers__text_utils__TitleCaseResponse
      Removed value: -{
-  "properties": {
-    "original": {
-      "description": "Original input text",
-      "title": "Original",
-      "type": "string"
-    },
-    "title_case": {
-      "description": "Text converted to smart title case (articles/prepositions lowercased)",
-      "title": "Title Case",
-      "type": "string"
-    }
-  },
-  "required": [
-    "original",
-    "title_case"
-  ],
-  "title": "TitleCaseResponse",
-  "type": "object"
-}
    • changedOutput schema / x-fastmcp-top-level-schema
      Previous value: -"app__routers__text_utils__TitleCaseResponse"New value: +"TitleCaseResponse"
  3. Changed3 schema fields changed
    • removedOutput schema / $defs / TitleCaseResponse
      Removed value: -{
-  "properties": {
-    "original": {
-      "description": "Original input text",
-      "title": "Original",
-      "type": "string"
-    },
-    "title_case": {
-      "description": "Text converted to smart title case (articles/prepositions lowercased)",
-      "title": "Title Case",
-      "type": "string"
-    }
-  },
-  "required": [
-    "original",
-    "title_case"
-  ],
-  "title": "TitleCaseResponse",
-  "type": "object"
-}
    • addedOutput schema / $defs / app__routers__text_utils__TitleCaseResponse
      Added value: +{
+  "properties": {
+    "original": {
+      "description": "Original input text",
+      "title": "Original",
+      "type": "string"
+    },
+    "title_case": {
+      "description": "Text converted to smart title case (articles/prepositions lowercased)",
+      "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__text_utils__TitleCaseResponse"
  4. Changed3 schema fields changed
    • addedOutput schema / $defs / TitleCaseResponse
      Added value: +{
+  "properties": {
+    "original": {
+      "description": "Original input text",
+      "title": "Original",
+      "type": "string"
+    },
+    "title_case": {
+      "description": "Text converted to smart title case (articles/prepositions lowercased)",
+      "title": "Title Case",
+      "type": "string"
+    }
+  },
+  "required": [
+    "original",
+    "title_case"
+  ],
+  "title": "TitleCaseResponse",
+  "type": "object"
+}
    • removedOutput schema / $defs / app__routers__text_utils__TitleCaseResponse
      Removed value: -{
-  "properties": {
-    "original": {
-      "description": "Original input text",
-      "title": "Original",
-      "type": "string"
-    },
-    "title_case": {
-      "description": "Text converted to smart title case (articles/prepositions lowercased)",
-      "title": "Title Case",
-      "type": "string"
-    }
-  },
-  "required": [
-    "original",
-    "title_case"
-  ],
-  "title": "TitleCaseResponse",
-  "type": "object"
-}
    • changedOutput schema / x-fastmcp-top-level-schema
      Previous value: -"app__routers__text_utils__TitleCaseResponse"New value: +"TitleCaseResponse"
  5. Changed3 schema fields changed
    • removedOutput schema / $defs / TitleCaseResponse
      Removed value: -{
-  "properties": {
-    "original": {
-      "description": "Original input text",
-      "title": "Original",
-      "type": "string"
-    },
-    "title_case": {
-      "description": "Text converted to smart title case (articles/prepositions lowercased)",
-      "title": "Title Case",
-      "type": "string"
-    }
-  },
-  "required": [
-    "original",
-    "title_case"
-  ],
-  "title": "TitleCaseResponse",
-  "type": "object"
-}
    • addedOutput schema / $defs / app__routers__text_utils__TitleCaseResponse
      Added value: +{
+  "properties": {
+    "original": {
+      "description": "Original input text",
+      "title": "Original",
+      "type": "string"
+    },
+    "title_case": {
+      "description": "Text converted to smart title case (articles/prepositions lowercased)",
+      "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__text_utils__TitleCaseResponse"
  6. First observed

TDQS

A3.5/5.0
Behavior3/5

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

With no annotations, the description carries the burden of disclosing behavior. It reveals the core transformation and the article/preposition handling, but it leaves ambiguity about the exact rules, such as whether first/last words are always capitalized and which words are lowercased.

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 extremely concise, front-loads the core behavior, and adds the distinguishing rule in a short parenthetical. There is no redundant content or repetition of schema details.

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?

For a one-parameter pure string transform with an output schema, much is covered. However, the 'smart' behavior is underspecified: an agent cannot fully infer the exact treatment of articles and prepositions or how this tool differs operationally from the plain title_case sibling.

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%, with the text parameter described as 'Text to convert'. The tool description adds the title-case intent but no additional format, encoding, or special-value guidance beyond what the schema already provides. This matches the baseline for high 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 identifies a title-casing transformation and the smart behavior of handling articles and prepositions. It lacks an explicit verb like 'converts', but the operation is unmistakable and the 'smart' qualifier distinguishes it from siblings such as title_case and 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 Guidelines3/5

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

The parenthetical implies the intended use: title casing where articles and prepositions receive special treatment. However, it never names alternative tools or states when to choose this one over them, leaving usage to inference rather than explicit guidance.

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