Skip to main content
Glama

TinyFn

by io.tinyfn
OverviewDiscussionsAdmin

is_palindrome

Check if text is a palindrome.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
textYesThe text to check
ignore_caseNoIgnore case
ignore_spacesNoIgnore spaces

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
textYes
is_palindromeYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • addedOutput schema / $defs / IsPalindromeResponse
      Added value: +{
+  "properties": {
+    "is_palindrome": {
+      "title": "Is Palindrome",
+      "type": "boolean"
+    },
+    "text": {
+      "title": "Text",
+      "type": "string"
+    }
+  },
+  "required": [
+    "text",
+    "is_palindrome"
+  ],
+  "title": "IsPalindromeResponse",
+  "type": "object"
+}
    • removedOutput schema / $defs / app__routers__string_utils__IsPalindromeResponse
      Removed value: -{
-  "properties": {
-    "is_palindrome": {
-      "title": "Is Palindrome",
-      "type": "boolean"
-    },
-    "text": {
-      "title": "Text",
-      "type": "string"
-    }
-  },
-  "required": [
-    "text",
-    "is_palindrome"
-  ],
-  "title": "IsPalindromeResponse",
-  "type": "object"
-}
    • changedOutput schema / x-fastmcp-top-level-schema
      Previous value: -"app__routers__string_utils__IsPalindromeResponse"New value: +"IsPalindromeResponse"
  2. Changed3 schema fields changed
    • removedOutput schema / $defs / IsPalindromeResponse
      Removed value: -{
-  "properties": {
-    "is_palindrome": {
-      "title": "Is Palindrome",
-      "type": "boolean"
-    },
-    "text": {
-      "title": "Text",
-      "type": "string"
-    }
-  },
-  "required": [
-    "text",
-    "is_palindrome"
-  ],
-  "title": "IsPalindromeResponse",
-  "type": "object"
-}
    • addedOutput schema / $defs / app__routers__string_utils__IsPalindromeResponse
      Added value: +{
+  "properties": {
+    "is_palindrome": {
+      "title": "Is Palindrome",
+      "type": "boolean"
+    },
+    "text": {
+      "title": "Text",
+      "type": "string"
+    }
+  },
+  "required": [
+    "text",
+    "is_palindrome"
+  ],
+  "title": "IsPalindromeResponse",
+  "type": "object"
+}
    • changedOutput schema / x-fastmcp-top-level-schema
      Previous value: -"IsPalindromeResponse"New value: +"app__routers__string_utils__IsPalindromeResponse"
  3. First observed

TDQS

B3.4/5.0
Behavior2/5

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

No annotations are provided, so the description must carry the behavioral burden. It fails to disclose that palindrome checking by default ignores case and spaces, and it does not mention edge cases such as empty strings or whitespace-only input.

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 a single front-loaded sentence with no filler or redundant details. It earns its place by stating the tool's core purpose immediately.

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?

With a fully described schema, an output schema present, and a simple operation, the description is mostly complete. A minor gap is that it does not explicitly mention the default normalization behavior, but the schema defaults compensate for that.

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 input schema provides 100% description coverage for all three parameters, including defaults for ignore_case and ignore_spaces. The description adds no parameter-specific meaning beyond the schema, so the baseline score of 3 applies.

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 uses a specific verb ('Check') and a specific resource ('text'), clearly stating the tool's operation. It also implicitly distinguishes itself from the sibling tool is_palindrome_number by referring to 'text' rather than numbers.

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?

The description gives no guidance on when to use this tool versus alternatives like is_palindrome_number, nor does it explain the significance of the ignore_case and ignore_spaces options. Usage is only implied by the name and simple purpose.

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
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources