Skip to main content
Glama

TinyFn

by io.tinyfn

sum_numbers

Calculate the sum of numbers.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
numbersYesComma-separated numbers

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
sumYes
numbersYes

Schema Changelog

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

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

TDQS

B3.4/5.0
Behavior3/5

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

No annotations are provided, so the description bears full burden. It only states the basic operation without revealing edge cases (e.g., handling of non-numeric input) or return format. For a simple mathematical function, this is minimally adequate but not detailed.

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

Conciseness5/5

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

The description is a single, front-loaded sentence with zero waste. It is appropriately concise for a simple 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 low complexity, rich schema, and presence of an output schema, the description is nearly complete. It could benefit from explicitly stating the input format expected, but overall it provides enough context for correct use.

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 covers the parameter 'numbers' with description 'Comma-separated numbers' (100% coverage). The description adds no additional meaning beyond the schema, so it meets the baseline but does not enhance understanding.

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 'Calculate the sum of numbers' clearly states the tool's purpose with a specific verb (calculate) and resource (sum of numbers). However, it does not explicitly mention that the input should be comma-separated, which is only in the schema. Still, it is clear enough to distinguish from other math tools.

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 is provided on when to use this tool versus siblings like 'add' or 'calculate_sum'. There are no usage examples or alternatives mentioned, leaving the agent to infer context from the tool name alone.

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