Skip to main content
Glama

TinyFn

by io.tinyfn
OverviewDiscussionsAdmin

calculate_sum

Calculate sum of numbers.

Input Schema

NameRequiredDescriptionDefault
numbersYesComma-separated numbers

Output Schema

NameRequiredDescriptionDefault
sumYes
countYes
numbersYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • 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"
  2. Changed3 schema fields changed
    • 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"
  3. Changed3 schema fields changed
    • 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"
  4. Changed3 schema fields changed
    • 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"
  5. Changed3 schema fields changed
    • 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"
  6. First observed

TDQS

C2.9/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 full burden. It only states purpose and does not disclose any behavioral traits such as return format, error handling, or performance implications.

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?

Single sentence, no wasted words. Efficiently communicates the core function.

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 and the existence of an output schema, the description is mostly complete. It could mention the return type (a number) but is adequate for a basic calculator.

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 description coverage is 100%, and the schema already describes 'numbers' as comma-separated. The description does not add meaning beyond 'Calculate sum of numbers'. Baseline 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?

Description states 'Calculate sum of numbers' which is clear but fails to differentiate from the sibling tool 'sum_numbers' that likely performs the same function. The tool's purpose is conveyed, but distinction is lacking.

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 vs alternatives like 'add' or 'sum_numbers'. No context on appropriate inputs or exclusions.

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
Shareable, User-Owned Context BackendPeople, applications, and agents read, write, and coordinate together in one context lake. Reach it over MCP, a CLI, a Python SDK, or REST.fulcradynamics.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources