Skip to main content
Glama

TinyFn

by io.tinyfn

truncate

Truncate to integer (remove decimal part).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
numberYesNumber to truncate

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 / TruncateResponse
      Removed value: -{
-  "properties": {
-    "number": {
-      "title": "Number",
-      "type": "number"
-    },
-    "result": {
-      "title": "Result",
-      "type": "integer"
-    }
-  },
-  "required": [
-    "number",
-    "result"
-  ],
-  "title": "TruncateResponse",
-  "type": "object"
-}
    • addedOutput schema / $defs / app__routers__math_utils__TruncateResponse
      Added value: +{
+  "properties": {
+    "number": {
+      "title": "Number",
+      "type": "number"
+    },
+    "result": {
+      "title": "Result",
+      "type": "integer"
+    }
+  },
+  "required": [
+    "number",
+    "result"
+  ],
+  "title": "TruncateResponse",
+  "type": "object"
+}
    • changedOutput schema / x-fastmcp-top-level-schema
      Previous value: -"TruncateResponse"New value: +"app__routers__math_utils__TruncateResponse"
  2. Changed3 schema fields changed
    • addedOutput schema / $defs / TruncateResponse
      Added value: +{
+  "properties": {
+    "number": {
+      "title": "Number",
+      "type": "number"
+    },
+    "result": {
+      "title": "Result",
+      "type": "integer"
+    }
+  },
+  "required": [
+    "number",
+    "result"
+  ],
+  "title": "TruncateResponse",
+  "type": "object"
+}
    • removedOutput schema / $defs / app__routers__math_utils__TruncateResponse
      Removed value: -{
-  "properties": {
-    "number": {
-      "title": "Number",
-      "type": "number"
-    },
-    "result": {
-      "title": "Result",
-      "type": "integer"
-    }
-  },
-  "required": [
-    "number",
-    "result"
-  ],
-  "title": "TruncateResponse",
-  "type": "object"
-}
    • changedOutput schema / x-fastmcp-top-level-schema
      Previous value: -"app__routers__math_utils__TruncateResponse"New value: +"TruncateResponse"
  3. Changed3 schema fields changed
    • removedOutput schema / $defs / TruncateResponse
      Removed value: -{
-  "properties": {
-    "number": {
-      "title": "Number",
-      "type": "number"
-    },
-    "result": {
-      "title": "Result",
-      "type": "integer"
-    }
-  },
-  "required": [
-    "number",
-    "result"
-  ],
-  "title": "TruncateResponse",
-  "type": "object"
-}
    • addedOutput schema / $defs / app__routers__math_utils__TruncateResponse
      Added value: +{
+  "properties": {
+    "number": {
+      "title": "Number",
+      "type": "number"
+    },
+    "result": {
+      "title": "Result",
+      "type": "integer"
+    }
+  },
+  "required": [
+    "number",
+    "result"
+  ],
+  "title": "TruncateResponse",
+  "type": "object"
+}
    • changedOutput schema / x-fastmcp-top-level-schema
      Previous value: -"TruncateResponse"New value: +"app__routers__math_utils__TruncateResponse"
  4. Changed3 schema fields changed
    • addedOutput schema / $defs / TruncateResponse
      Added value: +{
+  "properties": {
+    "number": {
+      "title": "Number",
+      "type": "number"
+    },
+    "result": {
+      "title": "Result",
+      "type": "integer"
+    }
+  },
+  "required": [
+    "number",
+    "result"
+  ],
+  "title": "TruncateResponse",
+  "type": "object"
+}
    • removedOutput schema / $defs / app__routers__math_utils__TruncateResponse
      Removed value: -{
-  "properties": {
-    "number": {
-      "title": "Number",
-      "type": "number"
-    },
-    "result": {
-      "title": "Result",
-      "type": "integer"
-    }
-  },
-  "required": [
-    "number",
-    "result"
-  ],
-  "title": "TruncateResponse",
-  "type": "object"
-}
    • changedOutput schema / x-fastmcp-top-level-schema
      Previous value: -"app__routers__math_utils__TruncateResponse"New value: +"TruncateResponse"
  5. Changed3 schema fields changed
    • removedOutput schema / $defs / TruncateResponse
      Removed value: -{
-  "properties": {
-    "number": {
-      "title": "Number",
-      "type": "number"
-    },
-    "result": {
-      "title": "Result",
-      "type": "integer"
-    }
-  },
-  "required": [
-    "number",
-    "result"
-  ],
-  "title": "TruncateResponse",
-  "type": "object"
-}
    • addedOutput schema / $defs / app__routers__math_utils__TruncateResponse
      Added value: +{
+  "properties": {
+    "number": {
+      "title": "Number",
+      "type": "number"
+    },
+    "result": {
+      "title": "Result",
+      "type": "integer"
+    }
+  },
+  "required": [
+    "number",
+    "result"
+  ],
+  "title": "TruncateResponse",
+  "type": "object"
+}
    • changedOutput schema / x-fastmcp-top-level-schema
      Previous value: -"TruncateResponse"New value: +"app__routers__math_utils__TruncateResponse"
  6. 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 provided, the description carries the burden of explaining behavior. It does state the core behavior ('remove decimal part') and implies truncation toward zero, but it does not explicitly address negative-number semantics or edge cases. Overall it is adequate but leaves some behavioral nuance unspoken.

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. The core behavior is front-loaded and the parenthetical clarifies the exact meaning.

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 simple pure mathematical function with one fully described parameter and an output schema, the description is nearly complete. The main missing piece is explicit differentiation from sibling truncation/rounding tools, but the tool's own contract is adequately covered.

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 the parameter is described as 'Number to truncate', so the schema already fully documents the only parameter. The description adds little semantic value 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 clearly states a specific operation ('Truncate to integer') and the mechanism ('remove decimal part'), so an agent can understand what the tool does. However, it does not differentiate this from closely related siblings like truncate_2, floor, or ceil.

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 guidance about when to use this tool instead of alternatives such as truncate_2, round_number, floor, or ceil. The behavior is implied by the description, but the agent is given no explicit selection criteria.

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