TinyFn

calculate_sum

Calculate sum of numbers.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`numbers`	Yes	Comma-separated numbers

Output Schema

TableJSON Schema

Name	Required	Description	Default
`sum`	Yes
`count`	Yes
`numbers`	Yes

Schema Changelog

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

Changed3 schema fields changedJul 27, 2026

addedOutput schema / $defs / SumResponse

Added value: +{
+  "properties": {
+    "count": {
+      "title": "Count",
+      "type": "integer"
+    },
+    "numbers": {
+      "items": {
+        "type": "number"
+      },
+      "title": "Numbers",
+      "type": "array"
+    },
+    "sum": {
+      "title": "Sum",
+      "type": "number"
+    }
+  },
+  "required": [
+    "numbers",
+    "count",
+    "sum"
+  ],
+  "title": "SumResponse",
+  "type": "object"
+}

removedOutput schema / $defs / app__routers__stats_utils__SumResponse

Removed value: -{
-  "properties": {
-    "count": {
-      "title": "Count",
-      "type": "integer"
-    },
-    "numbers": {
-      "items": {
-        "type": "number"
-      },
-      "title": "Numbers",
-      "type": "array"
-    },
-    "sum": {
-      "title": "Sum",
-      "type": "number"
-    }
-  },
-  "required": [
-    "numbers",
-    "count",
-    "sum"
-  ],
-  "title": "SumResponse",
-  "type": "object"
-}

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

Previous value: -"app__routers__stats_utils__SumResponse"New value: +"SumResponse"

Changed3 schema fields changedJul 17, 2026

removedOutput schema / $defs / SumResponse

Removed value: -{
-  "properties": {
-    "count": {
-      "title": "Count",
-      "type": "integer"
-    },
-    "numbers": {
-      "items": {
-        "type": "number"
-      },
-      "title": "Numbers",
-      "type": "array"
-    },
-    "sum": {
-      "title": "Sum",
-      "type": "number"
-    }
-  },
-  "required": [
-    "numbers",
-    "count",
-    "sum"
-  ],
-  "title": "SumResponse",
-  "type": "object"
-}

addedOutput schema / $defs / app__routers__stats_utils__SumResponse

Added value: +{
+  "properties": {
+    "count": {
+      "title": "Count",
+      "type": "integer"
+    },
+    "numbers": {
+      "items": {
+        "type": "number"
+      },
+      "title": "Numbers",
+      "type": "array"
+    },
+    "sum": {
+      "title": "Sum",
+      "type": "number"
+    }
+  },
+  "required": [
+    "numbers",
+    "count",
+    "sum"
+  ],
+  "title": "SumResponse",
+  "type": "object"
+}

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

Previous value: -"SumResponse"New value: +"app__routers__stats_utils__SumResponse"

Changed3 schema fields changedJul 13, 2026

addedOutput schema / $defs / SumResponse

Added value: +{
+  "properties": {
+    "count": {
+      "title": "Count",
+      "type": "integer"
+    },
+    "numbers": {
+      "items": {
+        "type": "number"
+      },
+      "title": "Numbers",
+      "type": "array"
+    },
+    "sum": {
+      "title": "Sum",
+      "type": "number"
+    }
+  },
+  "required": [
+    "numbers",
+    "count",
+    "sum"
+  ],
+  "title": "SumResponse",
+  "type": "object"
+}

removedOutput schema / $defs / app__routers__stats_utils__SumResponse

Removed value: -{
-  "properties": {
-    "count": {
-      "title": "Count",
-      "type": "integer"
-    },
-    "numbers": {
-      "items": {
-        "type": "number"
-      },
-      "title": "Numbers",
-      "type": "array"
-    },
-    "sum": {
-      "title": "Sum",
-      "type": "number"
-    }
-  },
-  "required": [
-    "numbers",
-    "count",
-    "sum"
-  ],
-  "title": "SumResponse",
-  "type": "object"
-}

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

Previous value: -"app__routers__stats_utils__SumResponse"New value: +"SumResponse"

Changed3 schema fields changedJul 8, 2026

removedOutput schema / $defs / SumResponse

Removed value: -{
-  "properties": {
-    "count": {
-      "title": "Count",
-      "type": "integer"
-    },
-    "numbers": {
-      "items": {
-        "type": "number"
-      },
-      "title": "Numbers",
-      "type": "array"
-    },
-    "sum": {
-      "title": "Sum",
-      "type": "number"
-    }
-  },
-  "required": [
-    "numbers",
-    "count",
-    "sum"
-  ],
-  "title": "SumResponse",
-  "type": "object"
-}

addedOutput schema / $defs / app__routers__stats_utils__SumResponse

Added value: +{
+  "properties": {
+    "count": {
+      "title": "Count",
+      "type": "integer"
+    },
+    "numbers": {
+      "items": {
+        "type": "number"
+      },
+      "title": "Numbers",
+      "type": "array"
+    },
+    "sum": {
+      "title": "Sum",
+      "type": "number"
+    }
+  },
+  "required": [
+    "numbers",
+    "count",
+    "sum"
+  ],
+  "title": "SumResponse",
+  "type": "object"
+}

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

Previous value: -"SumResponse"New value: +"app__routers__stats_utils__SumResponse"

First observedJun 27, 2026

TDQS

C2.8/5.0

Behavior2/5

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

No annotations provided, and the description does not disclose any behavioral traits beyond the basic operation. No mention of error handling, precision, or input validation.

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

Conciseness3/5

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

The description is very concise (one sentence), but it lacks necessary detail. It is under-specified rather than efficiently concise.

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

Completeness2/5

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

Given the simplicity of the tool and presence of output schema, the description could be complete, but it does not explain behavior for edge cases or differentiate from similar tools.

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 has 100% coverage describing the parameter as 'Comma-separated numbers'. The description adds no new meaning beyond the schema.

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?

Description clearly states the tool sums numbers, which matches the name. However, it does not distinguish from sibling tools like 'sum_numbers' or 'add', which perform similar operations.

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 explicit context or exclusions 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.

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.

calculate_sum

Input Schema

Output Schema

Schema Changelog

TDQS

Glama MCP Gateway

TDQS

Resources