Skip to main content
Glama

TinyFn

by io.tinyfn
OverviewDiscussionsAdmin

square

Calculate the square of a number.

Input Schema

NameRequiredDescriptionDefault
numberYesNumber to square

Output Schema

NameRequiredDescriptionDefault
numberYes
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. 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"
  2. 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"
  3. 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"
  4. 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"
  5. 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"
  6. 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"
  7. 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"
  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 burden, but for a pure single-value arithmetic function the behavior is inherently transparent and an output schema exists to describe the return. It adds no detail on edge cases such as negative inputs or very large numbers, which keeps it at minimum viable rather than strong.

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?

One sentence, front-loaded with the verb and resource, with zero redundant or padding content. Appropriately sized for a one-parameter math utility.

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 an output schema present and a fully documented single parameter, the description covers everything essential to invoke the tool correctly. Only minor edge-case behavior (negatives, precision) is left implicit, which is acceptable for this operation.

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% and there is a single required parameter documented as "Number to square". The description's "of a number" merely restates that, adding no format, range, or domain constraints beyond the schema.

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 names a specific verb and resource ("Calculate the square of a number"), which is unambiguous and actionable. It does not, however, distinguish this from close siblings such as cube, nth_square, square_root, or power, so an agent must infer the boundary from the names alone.

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 indication of when to use this over cube, nth_square, or power, nor any stated exclusions or prerequisites. The agent gets the operation but no routing guidance among the many numeric siblings.

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