TinyFn

in_range

Check if a value is within a range.

Input Schema

TableJSON Schema

Name	Required	Description
`value`	Yes	Value to check
`max_val`	Yes	Maximum value
`min_val`	Yes	Minimum value

Output Schema

TableJSON Schema

Name	Required	Description	Default
`max`	Yes
`min`	Yes
`value`	Yes
`in_range`	Yes
`distance_from_max`	Yes
`distance_from_min`	Yes

Schema Changelog

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

Changed3 schema fields changedAug 29, 2026

addedOutput schema / $defs / RangeResponse

Added value: +{
+  "properties": {
+    "distance_from_max": {
+      "title": "Distance From Max",
+      "type": "number"
+    },
+    "distance_from_min": {
+      "title": "Distance From Min",
+      "type": "number"
+    },
+    "in_range": {
+      "title": "In Range",
+      "type": "boolean"
+    },
+    "max": {
+      "title": "Max",
+      "type": "number"
+    },
+    "min": {
+      "title": "Min",
+      "type": "number"
+    },
+    "value": {
+      "title": "Value",
+      "type": "number"
+    }
+  },
+  "required": [
+    "value",
+    "min",
+    "max",
+    "in_range",
+    "distance_from_min",
+    "distance_from_max"
+  ],
+  "title": "RangeResponse",
+  "type": "object"
+}

removedOutput schema / $defs / app__routers__misc_utils__RangeResponse

Removed value: -{
-  "properties": {
-    "distance_from_max": {
-      "title": "Distance From Max",
-      "type": "number"
-    },
-    "distance_from_min": {
-      "title": "Distance From Min",
-      "type": "number"
-    },
-    "in_range": {
-      "title": "In Range",
-      "type": "boolean"
-    },
-    "max": {
-      "title": "Max",
-      "type": "number"
-    },
-    "min": {
-      "title": "Min",
-      "type": "number"
-    },
-    "value": {
-      "title": "Value",
-      "type": "number"
-    }
-  },
-  "required": [
-    "value",
-    "min",
-    "max",
-    "in_range",
-    "distance_from_min",
-    "distance_from_max"
-  ],
-  "title": "RangeResponse",
-  "type": "object"
-}

changedOutput schema / x-fastmcp-top-level-schema

Previous value: -"app__routers__misc_utils__RangeResponse"New value: +"RangeResponse"

Changed3 schema fields changedAug 29, 2026

removedOutput schema / $defs / RangeResponse

Removed value: -{
-  "properties": {
-    "distance_from_max": {
-      "title": "Distance From Max",
-      "type": "number"
-    },
-    "distance_from_min": {
-      "title": "Distance From Min",
-      "type": "number"
-    },
-    "in_range": {
-      "title": "In Range",
-      "type": "boolean"
-    },
-    "max": {
-      "title": "Max",
-      "type": "number"
-    },
-    "min": {
-      "title": "Min",
-      "type": "number"
-    },
-    "value": {
-      "title": "Value",
-      "type": "number"
-    }
-  },
-  "required": [
-    "value",
-    "min",
-    "max",
-    "in_range",
-    "distance_from_min",
-    "distance_from_max"
-  ],
-  "title": "RangeResponse",
-  "type": "object"
-}

addedOutput schema / $defs / app__routers__misc_utils__RangeResponse

Added value: +{
+  "properties": {
+    "distance_from_max": {
+      "title": "Distance From Max",
+      "type": "number"
+    },
+    "distance_from_min": {
+      "title": "Distance From Min",
+      "type": "number"
+    },
+    "in_range": {
+      "title": "In Range",
+      "type": "boolean"
+    },
+    "max": {
+      "title": "Max",
+      "type": "number"
+    },
+    "min": {
+      "title": "Min",
+      "type": "number"
+    },
+    "value": {
+      "title": "Value",
+      "type": "number"
+    }
+  },
+  "required": [
+    "value",
+    "min",
+    "max",
+    "in_range",
+    "distance_from_min",
+    "distance_from_max"
+  ],
+  "title": "RangeResponse",
+  "type": "object"
+}

changedOutput schema / x-fastmcp-top-level-schema

Previous value: -"RangeResponse"New value: +"app__routers__misc_utils__RangeResponse"

Changed3 schema fields changedJul 27, 2026

addedOutput schema / $defs / RangeResponse

Added value: +{
+  "properties": {
+    "distance_from_max": {
+      "title": "Distance From Max",
+      "type": "number"
+    },
+    "distance_from_min": {
+      "title": "Distance From Min",
+      "type": "number"
+    },
+    "in_range": {
+      "title": "In Range",
+      "type": "boolean"
+    },
+    "max": {
+      "title": "Max",
+      "type": "number"
+    },
+    "min": {
+      "title": "Min",
+      "type": "number"
+    },
+    "value": {
+      "title": "Value",
+      "type": "number"
+    }
+  },
+  "required": [
+    "value",
+    "min",
+    "max",
+    "in_range",
+    "distance_from_min",
+    "distance_from_max"
+  ],
+  "title": "RangeResponse",
+  "type": "object"
+}

removedOutput schema / $defs / app__routers__misc_utils__RangeResponse

Removed value: -{
-  "properties": {
-    "distance_from_max": {
-      "title": "Distance From Max",
-      "type": "number"
-    },
-    "distance_from_min": {
-      "title": "Distance From Min",
-      "type": "number"
-    },
-    "in_range": {
-      "title": "In Range",
-      "type": "boolean"
-    },
-    "max": {
-      "title": "Max",
-      "type": "number"
-    },
-    "min": {
-      "title": "Min",
-      "type": "number"
-    },
-    "value": {
-      "title": "Value",
-      "type": "number"
-    }
-  },
-  "required": [
-    "value",
-    "min",
-    "max",
-    "in_range",
-    "distance_from_min",
-    "distance_from_max"
-  ],
-  "title": "RangeResponse",
-  "type": "object"
-}

changedOutput schema / x-fastmcp-top-level-schema

Previous value: -"app__routers__misc_utils__RangeResponse"New value: +"RangeResponse"

Changed3 schema fields changedJul 27, 2026

removedOutput schema / $defs / RangeResponse

Removed value: -{
-  "properties": {
-    "distance_from_max": {
-      "title": "Distance From Max",
-      "type": "number"
-    },
-    "distance_from_min": {
-      "title": "Distance From Min",
-      "type": "number"
-    },
-    "in_range": {
-      "title": "In Range",
-      "type": "boolean"
-    },
-    "max": {
-      "title": "Max",
-      "type": "number"
-    },
-    "min": {
-      "title": "Min",
-      "type": "number"
-    },
-    "value": {
-      "title": "Value",
-      "type": "number"
-    }
-  },
-  "required": [
-    "value",
-    "min",
-    "max",
-    "in_range",
-    "distance_from_min",
-    "distance_from_max"
-  ],
-  "title": "RangeResponse",
-  "type": "object"
-}

addedOutput schema / $defs / app__routers__misc_utils__RangeResponse

Added value: +{
+  "properties": {
+    "distance_from_max": {
+      "title": "Distance From Max",
+      "type": "number"
+    },
+    "distance_from_min": {
+      "title": "Distance From Min",
+      "type": "number"
+    },
+    "in_range": {
+      "title": "In Range",
+      "type": "boolean"
+    },
+    "max": {
+      "title": "Max",
+      "type": "number"
+    },
+    "min": {
+      "title": "Min",
+      "type": "number"
+    },
+    "value": {
+      "title": "Value",
+      "type": "number"
+    }
+  },
+  "required": [
+    "value",
+    "min",
+    "max",
+    "in_range",
+    "distance_from_min",
+    "distance_from_max"
+  ],
+  "title": "RangeResponse",
+  "type": "object"
+}

changedOutput schema / x-fastmcp-top-level-schema

Previous value: -"RangeResponse"New value: +"app__routers__misc_utils__RangeResponse"

Changed3 schema fields changedJul 20, 2026

addedOutput schema / $defs / RangeResponse

Added value: +{
+  "properties": {
+    "distance_from_max": {
+      "title": "Distance From Max",
+      "type": "number"
+    },
+    "distance_from_min": {
+      "title": "Distance From Min",
+      "type": "number"
+    },
+    "in_range": {
+      "title": "In Range",
+      "type": "boolean"
+    },
+    "max": {
+      "title": "Max",
+      "type": "number"
+    },
+    "min": {
+      "title": "Min",
+      "type": "number"
+    },
+    "value": {
+      "title": "Value",
+      "type": "number"
+    }
+  },
+  "required": [
+    "value",
+    "min",
+    "max",
+    "in_range",
+    "distance_from_min",
+    "distance_from_max"
+  ],
+  "title": "RangeResponse",
+  "type": "object"
+}

removedOutput schema / $defs / app__routers__misc_utils__RangeResponse

Removed value: -{
-  "properties": {
-    "distance_from_max": {
-      "title": "Distance From Max",
-      "type": "number"
-    },
-    "distance_from_min": {
-      "title": "Distance From Min",
-      "type": "number"
-    },
-    "in_range": {
-      "title": "In Range",
-      "type": "boolean"
-    },
-    "max": {
-      "title": "Max",
-      "type": "number"
-    },
-    "min": {
-      "title": "Min",
-      "type": "number"
-    },
-    "value": {
-      "title": "Value",
-      "type": "number"
-    }
-  },
-  "required": [
-    "value",
-    "min",
-    "max",
-    "in_range",
-    "distance_from_min",
-    "distance_from_max"
-  ],
-  "title": "RangeResponse",
-  "type": "object"
-}

changedOutput schema / x-fastmcp-top-level-schema

Previous value: -"app__routers__misc_utils__RangeResponse"New value: +"RangeResponse"

First observedJun 27, 2026

TDQS

C2.9/5.0

Behavior2/5

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

With no annotations, the description fully carries the burden, but it does not disclose whether boundaries are inclusive/exclusive, the return type, or edge cases. This is insufficient for a tool with no annotation support.

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 sentence with no unnecessary words. It is concise, though it could benefit from more structured information.

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?

For a simple numeric range check, the description covers the basic purpose. However, missing details like inclusive/exclusive boundaries and lack of differentiation from 'is_between' leave gaps.

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%, and each parameter already has a basic description. The tool description adds no additional meaning beyond what the schema provides, so baseline 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 clearly states the tool checks if a value is within a range, using a specific verb and resource. However, it does not differentiate from sibling tools like 'is_between', which likely have the same purpose.

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?

No guidance on when to use this tool versus alternatives. No prerequisites, exclusions, or examples are provided.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All TinyFn tools Inspect

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.

in_range

Input Schema

Output Schema

Schema Changelog

TDQS

Glama MCP Gateway

TDQS

Resources