Skip to main content
Glama

TinyFn

by io.tinyfn

minimum

Find the minimum value.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
numbersYesComma-separated numbers

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
minYes
numbersYes

Schema Changelog

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

  1. Changed3 schema fields changed
    • addedOutput schema / $defs / MinResponse
      Added value: +{
+  "properties": {
+    "min": {
+      "title": "Min",
+      "type": "number"
+    },
+    "numbers": {
+      "items": {
+        "type": "number"
+      },
+      "title": "Numbers",
+      "type": "array"
+    }
+  },
+  "required": [
+    "numbers",
+    "min"
+  ],
+  "title": "MinResponse",
+  "type": "object"
+}
    • removedOutput schema / $defs / app__routers__math_utils__MinResponse
      Removed value: -{
-  "properties": {
-    "min": {
-      "title": "Min",
-      "type": "number"
-    },
-    "numbers": {
-      "items": {
-        "type": "number"
-      },
-      "title": "Numbers",
-      "type": "array"
-    }
-  },
-  "required": [
-    "numbers",
-    "min"
-  ],
-  "title": "MinResponse",
-  "type": "object"
-}
    • changedOutput schema / x-fastmcp-top-level-schema
      Previous value: -"app__routers__math_utils__MinResponse"New value: +"MinResponse"
  2. Changed3 schema fields changed
    • removedOutput schema / $defs / MinResponse
      Removed value: -{
-  "properties": {
-    "min": {
-      "title": "Min",
-      "type": "number"
-    },
-    "numbers": {
-      "items": {
-        "type": "number"
-      },
-      "title": "Numbers",
-      "type": "array"
-    }
-  },
-  "required": [
-    "numbers",
-    "min"
-  ],
-  "title": "MinResponse",
-  "type": "object"
-}
    • addedOutput schema / $defs / app__routers__math_utils__MinResponse
      Added value: +{
+  "properties": {
+    "min": {
+      "title": "Min",
+      "type": "number"
+    },
+    "numbers": {
+      "items": {
+        "type": "number"
+      },
+      "title": "Numbers",
+      "type": "array"
+    }
+  },
+  "required": [
+    "numbers",
+    "min"
+  ],
+  "title": "MinResponse",
+  "type": "object"
+}
    • changedOutput schema / x-fastmcp-top-level-schema
      Previous value: -"MinResponse"New value: +"app__routers__math_utils__MinResponse"
  3. Changed3 schema fields changed
    • addedOutput schema / $defs / MinResponse
      Added value: +{
+  "properties": {
+    "min": {
+      "title": "Min",
+      "type": "number"
+    },
+    "numbers": {
+      "items": {
+        "type": "number"
+      },
+      "title": "Numbers",
+      "type": "array"
+    }
+  },
+  "required": [
+    "numbers",
+    "min"
+  ],
+  "title": "MinResponse",
+  "type": "object"
+}
    • removedOutput schema / $defs / app__routers__math_utils__MinResponse
      Removed value: -{
-  "properties": {
-    "min": {
-      "title": "Min",
-      "type": "number"
-    },
-    "numbers": {
-      "items": {
-        "type": "number"
-      },
-      "title": "Numbers",
-      "type": "array"
-    }
-  },
-  "required": [
-    "numbers",
-    "min"
-  ],
-  "title": "MinResponse",
-  "type": "object"
-}
    • changedOutput schema / x-fastmcp-top-level-schema
      Previous value: -"app__routers__math_utils__MinResponse"New value: +"MinResponse"
  4. First observed

TDQS

B3.2/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 full burden of behavioral disclosure. It states the core computation but does not mention behavior for empty input, malformed numbers, whitespace, or whether all values must be numeric. This is acceptable for such a simple pure function, but not fully transparent.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is only four words and every word is functional. It is appropriately sized for a simple tool, though the brevity comes at the cost of usage guidance and edge-case transparency. It is concise without being as useless as a pure tautology.

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 one-parameter pure function, the description plus a fully detailed schema is enough for an agent to invoke it correctly in normal cases. An output schema exists, so return-value documentation is not required. It is less complete for choosing between sibling min-like tools, but that is a selection concern rather than a calling concern.

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 'numbers' parameter as 'Comma-separated numbers,' giving 100% schema description coverage. The description adds no additional meaning about accepted number types, negative values, or parsing behavior, so the baseline 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 clear verb and resource: 'Find the minimum value.' An agent can understand what the tool does. However, it does not differentiate this tool from the sibling min_value, or explain how it relates to max_value/average, so it is clear but not sibling-distinguishing.

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 this tool versus alternatives such as min_value, max_value, average, or sort_items. It gives no context about intended use, exclusions, or conditions that would make another tool more appropriate. The usage is only implied by the 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