calculate_mean
Calculate arithmetic mean (average).
Input Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| numbers | Yes | Comma-separated numbers |
Output Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| mean | Yes | ||
| count | Yes | ||
| numbers | Yes |
TinyFn
by io.tinyfn
Schema Changelog
Changes observed during successful MCP inspections. Dates show when Glama detected each change.
- First observed
TDQS
B3.3/5.0
Behavior2/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description must bear the full burden. It only states the core function without disclosing how edge cases (e.g., empty input, non-numeric values) are handled or any limitations.
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 concise sentence that conveys the essential purpose without any extraneous words. It is front-loaded and efficient.
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 arithmetic tool with an output schema, the description combined with the schema covers the basics. However, it lacks context about return values or edge cases, meriting an average score.
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 single parameter 'numbers' is fully described in the input schema as 'Comma-separated numbers', so the description adds no additional meaning. With 100% schema coverage, baseline 3 is appropriate.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Purpose5/5
Does the description clearly state what the tool does and how it differs from similar tools?
The description 'Calculate arithmetic mean (average)' clearly states the specific verb 'Calculate' and resource 'arithmetic mean', distinguishing it from sibling tools like calculate_median and calculate_mode.
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 such as median or mode. The description does not mention any conditions or context for appropriate usage.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Try in Browser
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.