Skip to main content
Glama

TinyFn

by io.tinyfn

maximum

Find the maximum value.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
numbersYesComma-separated numbers

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
maxYes
numbersYes

Schema Changelog

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

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

TDQS

C2.7/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full behavioral disclosure burden. It only states the basic operation and does not explain parsing expectations, handling of empty or invalid input, or error behavior. It adds almost no behavioral context beyond what the tool name already implies.

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 a single front-loaded sentence with no filler. For a tool with one simple parameter, this brevity is mostly appropriate, though it is so terse that it borders on under-specification rather than useful conciseness.

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?

The input and output schemas cover the basic mechanics, and the tool is low complexity, so the description is minimally viable. However, it lacks the context needed to disambiguate from max_value and to confirm exactly what input it operates on, leaving clear gaps for agent decision-making.

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 provides 100% description coverage for the only parameter, 'numbers', as comma-separated numbers. The description adds no parameter-specific meaning, but the schema already carries the load, 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.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description uses a verb ('Find') and names the outcome ('maximum value'), but it does not specify that the subject is the comma-separated numbers input. It also does not distinguish this tool from the sibling max_value, leaving real ambiguity about which 'maximum' tool is intended.

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 maximum versus max_value, minimum, average, or other similar aggregation tools. The only implied usage is the word 'maximum', which is not enough for an agent to confidently choose among closely related 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
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