Skip to main content
Glama

TinyFn

by io.tinyfn
OverviewDiscussionsAdmin

is_palindrome_number

Check if a number is a palindrome.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
numberYesNumber to check

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
numberYes
reversedYes
is_palindromeYes

Schema Changelog

Changes observed during successful MCP inspections.

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

TDQS

B3.4/5.0
Behavior3/5

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

With no annotations, the description is the main behavioral source. It correctly conveys that this is a read-only predicate, but it does not clarify edge-case behavior such as how negative numbers are treated or whether the leading minus sign is considered.

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 focused sentence with no filler. It immediately communicates the operation and every word contributes to understanding.

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 predicate with an output schema, the description is nearly complete for invoking the tool. It lacks explicit sibling differentiation and negative-number handling, but the core call is clear.

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 already fully documents the single parameter as 'Number to check' with 100% coverage. The description adds no additional parameter semantics beyond restating the general operation, so the schema-covered baseline of 3 is appropriate.

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 states a clear verb and resource: check if a number is a palindrome. It is distinguishable from the sibling is_palindrome by the explicit focus on numbers, but it does not explicitly call out that difference.

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?

No guidance is provided on when to use this tool versus the very similar sibling is_palindrome or other number-predicate tools. The intended context is inferable from the name, but the description does not state exclusions or alternatives.

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