Skip to main content
Glama

TinyFn

by io.tinyfn

nth_square

Get the nth square number.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nYesWhich square number

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
nYes
squareYes

Schema Changelog

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

  1. Changed3 schema fields changed
    • addedOutput schema / $defs / SquareResponse
      Added value: +{
+  "properties": {
+    "n": {
+      "title": "N",
+      "type": "integer"
+    },
+    "square": {
+      "title": "Square",
+      "type": "integer"
+    }
+  },
+  "required": [
+    "n",
+    "square"
+  ],
+  "title": "SquareResponse",
+  "type": "object"
+}
    • removedOutput schema / $defs / app__routers__number_utils__SquareResponse
      Removed value: -{
-  "properties": {
-    "n": {
-      "title": "N",
-      "type": "integer"
-    },
-    "square": {
-      "title": "Square",
-      "type": "integer"
-    }
-  },
-  "required": [
-    "n",
-    "square"
-  ],
-  "title": "SquareResponse",
-  "type": "object"
-}
    • changedOutput schema / x-fastmcp-top-level-schema
      Previous value: -"app__routers__number_utils__SquareResponse"New value: +"SquareResponse"
  2. Changed3 schema fields changed
    • removedOutput schema / $defs / SquareResponse
      Removed value: -{
-  "properties": {
-    "n": {
-      "title": "N",
-      "type": "integer"
-    },
-    "square": {
-      "title": "Square",
-      "type": "integer"
-    }
-  },
-  "required": [
-    "n",
-    "square"
-  ],
-  "title": "SquareResponse",
-  "type": "object"
-}
    • addedOutput schema / $defs / app__routers__number_utils__SquareResponse
      Added value: +{
+  "properties": {
+    "n": {
+      "title": "N",
+      "type": "integer"
+    },
+    "square": {
+      "title": "Square",
+      "type": "integer"
+    }
+  },
+  "required": [
+    "n",
+    "square"
+  ],
+  "title": "SquareResponse",
+  "type": "object"
+}
    • changedOutput schema / x-fastmcp-top-level-schema
      Previous value: -"SquareResponse"New value: +"app__routers__number_utils__SquareResponse"
  3. Changed3 schema fields changed
    • addedOutput schema / $defs / SquareResponse
      Added value: +{
+  "properties": {
+    "n": {
+      "title": "N",
+      "type": "integer"
+    },
+    "square": {
+      "title": "Square",
+      "type": "integer"
+    }
+  },
+  "required": [
+    "n",
+    "square"
+  ],
+  "title": "SquareResponse",
+  "type": "object"
+}
    • removedOutput schema / $defs / app__routers__number_utils__SquareResponse
      Removed value: -{
-  "properties": {
-    "n": {
-      "title": "N",
-      "type": "integer"
-    },
-    "square": {
-      "title": "Square",
-      "type": "integer"
-    }
-  },
-  "required": [
-    "n",
-    "square"
-  ],
-  "title": "SquareResponse",
-  "type": "object"
-}
    • changedOutput schema / x-fastmcp-top-level-schema
      Previous value: -"app__routers__number_utils__SquareResponse"New value: +"SquareResponse"
  4. Changed3 schema fields changed
    • removedOutput schema / $defs / SquareResponse
      Removed value: -{
-  "properties": {
-    "n": {
-      "title": "N",
-      "type": "integer"
-    },
-    "square": {
-      "title": "Square",
-      "type": "integer"
-    }
-  },
-  "required": [
-    "n",
-    "square"
-  ],
-  "title": "SquareResponse",
-  "type": "object"
-}
    • addedOutput schema / $defs / app__routers__number_utils__SquareResponse
      Added value: +{
+  "properties": {
+    "n": {
+      "title": "N",
+      "type": "integer"
+    },
+    "square": {
+      "title": "Square",
+      "type": "integer"
+    }
+  },
+  "required": [
+    "n",
+    "square"
+  ],
+  "title": "SquareResponse",
+  "type": "object"
+}
    • changedOutput schema / x-fastmcp-top-level-schema
      Previous value: -"SquareResponse"New value: +"app__routers__number_utils__SquareResponse"
  5. Changed3 schema fields changed
    • addedOutput schema / $defs / SquareResponse
      Added value: +{
+  "properties": {
+    "n": {
+      "title": "N",
+      "type": "integer"
+    },
+    "square": {
+      "title": "Square",
+      "type": "integer"
+    }
+  },
+  "required": [
+    "n",
+    "square"
+  ],
+  "title": "SquareResponse",
+  "type": "object"
+}
    • removedOutput schema / $defs / app__routers__number_utils__SquareResponse
      Removed value: -{
-  "properties": {
-    "n": {
-      "title": "N",
-      "type": "integer"
-    },
-    "square": {
-      "title": "Square",
-      "type": "integer"
-    }
-  },
-  "required": [
-    "n",
-    "square"
-  ],
-  "title": "SquareResponse",
-  "type": "object"
-}
    • changedOutput schema / x-fastmcp-top-level-schema
      Previous value: -"app__routers__number_utils__SquareResponse"New value: +"SquareResponse"
  6. Changed3 schema fields changed
    • removedOutput schema / $defs / SquareResponse
      Removed value: -{
-  "properties": {
-    "n": {
-      "title": "N",
-      "type": "integer"
-    },
-    "square": {
-      "title": "Square",
-      "type": "integer"
-    }
-  },
-  "required": [
-    "n",
-    "square"
-  ],
-  "title": "SquareResponse",
-  "type": "object"
-}
    • addedOutput schema / $defs / app__routers__number_utils__SquareResponse
      Added value: +{
+  "properties": {
+    "n": {
+      "title": "N",
+      "type": "integer"
+    },
+    "square": {
+      "title": "Square",
+      "type": "integer"
+    }
+  },
+  "required": [
+    "n",
+    "square"
+  ],
+  "title": "SquareResponse",
+  "type": "object"
+}
    • changedOutput schema / x-fastmcp-top-level-schema
      Previous value: -"SquareResponse"New value: +"app__routers__number_utils__SquareResponse"
  7. First observed

TDQS

C2.4/5.0
Behavior1/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 disclosing behavior. It only says 'Get the nth square number' and reveals nothing about edge cases, return type, performance, or side effects. It is a pure function but this is not explicitly stated, and there is no mention of constraints or any behavioral traits beyond the obvious.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single short sentence, which is efficient and front-loaded. However, it is so minimal that it lacks structure or helpful elaboration; it is concise but not necessarily well-structured for an agent to quickly grasp usage nuances.

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

Completeness2/5

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

For a simple math tool with one parameter and an output schema, the description is arguably complete in the most basic sense. However, it fails to provide any contextual differentiation from siblings, any edge-case behavior (e.g., error on out-of-range), or any examples. Given the availability of a large sibling set, this lack of context makes the tool harder to select correctly.

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 provides a description for the parameter 'n' ('Which square number') and min/max constraints, so coverage is 100%. The tool description adds no extra meaning about the parameter beyond what the schema states, so it stays at the baseline of 3 without adding value.

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 the operation (get) and the resource (nth square number), which distinguishes it from the direct 'square' sibling. However, it does not explicitly differentiate itself from other nth-* tools like nth_cube or nth_prime, so it slightly misses on explicit sibling differentiation.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines1/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. No mention of cases where 'square' or other nth functions would be more appropriate, nor any context about typical use cases or prerequisites. The description offers zero usage direction.

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