Skip to main content
Glama

TinyFn

by io.tinyfn

square

Calculate the square of a number.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
numberYesNumber to square

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
numberYes
resultYes

Schema Changelog

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

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

TDQS

A3.7/5.0
Behavior4/5

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

With no annotations provided, the description must carry the behavioral burden. It clearly states the operation is squaring a number, which is a pure, side-effect-free computation. While it does not spell out edge cases or return formatting, the output schema exists and the behavior is sufficiently transparent for such a simple operation.

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 sentence with no wasted words, and the core operation is stated immediately. It is concise, scannable, and easy for an agent to parse.

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

Completeness5/5

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

The tool has a single fully documented parameter, an output schema, and a trivial pure computation. The description, combined with the schema and output schema, provides enough context for an agent to call this tool correctly. Nothing important 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?

The input schema already fully documents the single 'number' parameter with 100% coverage, including a description of 'Number to square'. The tool description does not add extra parameter semantics beyond what the schema provides, so the baseline score 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 specific verb and resource: 'Calculate the square of a number.' This clearly conveys the mathematical operation. It does not explicitly distinguish itself from related siblings like 'power', 'nth_square', or 'multiply', so it stops short of a 5.

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 about when to use this tool versus alternatives. It does not mention related tools like 'power', 'nth_square', or 'square_root', nor does it state when not to use it. The intended usage is only implied by the tool's 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
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