Skip to main content
Glama

TinyFn

by io.tinyfn

calculate_range

Calculate range (max - min).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
numbersYesComma-separated numbers

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
maxYes
minYes
rangeYes
numbersYes

Schema Changelog

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

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

TDQS

A3.5/5.0
Behavior2/5

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

No annotations are provided, so the description bears full responsibility for disclosing behavioral traits. It only states the basic operation, omitting details like return format, error handling (e.g., empty input), or whether the tool handles non-numeric values.

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, efficient sentence with no wasted words. However, it lacks any additional context (e.g., edge cases, examples) that might help, but remains appropriately sized for a straightforward mathematical tool.

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?

Given the tool's simplicity (one parameter, output schema exists), the description is mostly complete. The output schema likely specifies the return format, so the description does not need to explain that. Some minor gaps (e.g., handling of invalid input) are acceptable for a basic calculation.

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 coverage is 100% with the 'numbers' parameter having a clear description ('Comma-separated numbers'). The tool description adds no further meaning beyond what the schema already provides, so baseline score of 3 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

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

The description explicitly states the tool calculates range as 'max - min', which is a clear verb-resource pair. Among sibling tools with similar names (e.g., calculate_sum, calculate_mean), this description uniquely identifies the operation.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies usage for computing the range of numbers, but provides no explicit guidance on when to use this tool versus alternatives (e.g., calculate_mean, calculate_stddev) or any conditions for appropriate use.

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