Skip to main content
Glama

TinyFn

by io.tinyfn
OverviewDiscussionsAdmin

truncate

Truncate to integer (remove decimal part).

Input Schema

NameRequiredDescriptionDefault
numberYesNumber to truncate

Output Schema

NameRequiredDescriptionDefault
numberYes
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

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

TDQS

B3.3/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. It does disclose the core semantics ('remove decimal part'), but it leaves the negative-input behavior unstated, which is the one behavioral ambiguity of truncation. For a pure, side-effect-free math function this is a moderate gap rather than a fatal one.

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 short sentence with the operation front-loaded and the clarifying definition attached. Nothing extraneous.

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

Completeness3/5

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

An output schema exists and the tool is trivial, so little needs explaining. However, the description omits the negative-number semantics and any routing signal relative to floor/round_number, which are the only things an agent would actually get wrong here.

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 single parameter is already documented as 'Number to truncate'. The description adds no format, range, or type detail beyond the schema, so the baseline 3 applies.

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?

States a specific verb and result ('truncate to integer') with a clarifying parenthetical that defines the operation as removing the decimal part. It does not distinguish this from sibling math tools like floor, ceil, or round_number, which matter for negative numbers.

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 on when to use truncate versus floor, round_number, or the sibling truncate_2. The agent must infer the choice, and the negative-number case (truncate toward zero vs. floor toward negative infinity) is exactly where the choice matters.

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