Skip to main content
Glama

TinyFn

by io.tinyfn
OverviewDiscussionsAdmin

nth_square

Get the nth square number.

Input Schema

NameRequiredDescriptionDefault
nYesWhich square number

Output Schema

NameRequiredDescriptionDefault
nYes
squareYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. 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"
  2. 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"
  3. 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"
  4. 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"
  5. 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"
  6. 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"
  7. 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"
  8. First observed

TDQS

B3.4/5.0
Behavior3/5

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

No annotations are provided, so the description carries the behavioral burden. "Get" implies a read-only pure computation, and the schema bounds n, but the description does not explicitly state determinism, error behavior, or absence of side effects.

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 wasted words. It is appropriately sized for a simple one-parameter math tool.

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?

Given the tool's simplicity, one parameter, and the presence of an output schema, the description is nearly complete. It could be improved by clarifying the relationship to the square sibling tool, but nothing essential for invocation is missing.

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 description coverage is 100%, so the parameter semantics are already documented. The description adds no additional information about n beyond what the input schema provides.

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 uses a specific verb and resource: "Get the nth square number." It clearly states the computation, but it does not distinguish this from sibling tools such as square or is_perfect_square.

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 explicit guidance on when to use this tool versus alternatives like square or nth_cube. Usage is only implied by the function name and description.

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
Shareable, User-Owned Context BackendPeople, applications, and agents read, write, and coordinate together in one context lake. Reach it over MCP, a CLI, a Python SDK, or REST.fulcradynamics.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources