Skip to main content
Glama

TinyFn

by io.tinyfn
OverviewDiscussionsAdmin

sum_numbers

Calculate the sum of numbers.

Input Schema

NameRequiredDescriptionDefault
numbersYesComma-separated numbers

Output Schema

NameRequiredDescriptionDefault
sumYes
numbersYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. 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"
  2. 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"
  3. 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"
  4. 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"
  5. 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"
  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 present, so the description carries the full burden. It does not disclose behaviors such as handling of invalid input, negative numbers, overflow, or return type. With zero annotation coverage, the description fails to provide essential behavioral context.

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 a single sentence, which is concise but lacks structure. It would benefit from additional sentences to cover usage and behavior. The brevity does not fully serve the agent's needs.

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?

Given the tool's simplicity and the presence of an output schema, the description is minimally adequate. However, it does not explain edge cases or provide enough context for an agent to use it confidently, especially with similar sibling 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?

The input schema covers the single parameter with description 'Comma-separated numbers' (100% coverage). The tool description adds no additional meaning beyond what the schema already provides, so a baseline score of 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 action ('Calculate the sum of numbers') and the resource ('numbers'). However, it does not distinguish from sibling tools like 'add' or 'calculate_sum', which may perform similar operations. The verb+resource combination is specific but lacks scope differentiation.

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 alternatives. For instance, 'add' might handle two numbers while 'sum_numbers' handles a list, but this is not mentioned. There is no description of context 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