Skip to main content
Glama

TinyFn

cube

Calculate the cube of a number.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "number": "<number>"
    },
    "name": "cube"
  }
}

Input Schema

NameRequiredDescriptionDefault
numberYesNumber to cube

Output Schema

NameRequiredDescriptionDefault
numberYes
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • removedOutput schema / $defs / CubeResponse
      Removed value: -{
      -  "properties": {
      -    "number": {
      -      "title": "Number",
      -      "type": "number"
      -    },
      -    "result": {
      -      "title": "Result",
      -      "type": "number"
      -    }
      -  },
      -  "required": [
      -    "number",
      -    "result"
      -  ],
      -  "title": "CubeResponse",
      -  "type": "object"
      -}
    • addedOutput schema / $defs / app__routers__math_utils__CubeResponse
      Added value: +{
      +  "properties": {
      +    "number": {
      +      "title": "Number",
      +      "type": "number"
      +    },
      +    "result": {
      +      "title": "Result",
      +      "type": "number"
      +    }
      +  },
      +  "required": [
      +    "number",
      +    "result"
      +  ],
      +  "title": "CubeResponse",
      +  "type": "object"
      +}
    • changedOutput schema / x-fastmcp-top-level-schema
      Previous value: -"CubeResponse"New value: +"app__routers__math_utils__CubeResponse"
  2. Changed3 schema fields changed
    • addedOutput schema / $defs / CubeResponse
      Added value: +{
      +  "properties": {
      +    "number": {
      +      "title": "Number",
      +      "type": "number"
      +    },
      +    "result": {
      +      "title": "Result",
      +      "type": "number"
      +    }
      +  },
      +  "required": [
      +    "number",
      +    "result"
      +  ],
      +  "title": "CubeResponse",
      +  "type": "object"
      +}
    • removedOutput schema / $defs / app__routers__math_utils__CubeResponse
      Removed value: -{
      -  "properties": {
      -    "number": {
      -      "title": "Number",
      -      "type": "number"
      -    },
      -    "result": {
      -      "title": "Result",
      -      "type": "number"
      -    }
      -  },
      -  "required": [
      -    "number",
      -    "result"
      -  ],
      -  "title": "CubeResponse",
      -  "type": "object"
      -}
    • changedOutput schema / x-fastmcp-top-level-schema
      Previous value: -"app__routers__math_utils__CubeResponse"New value: +"CubeResponse"
  3. Changed3 schema fields changed
    • removedOutput schema / $defs / CubeResponse
      Removed value: -{
      -  "properties": {
      -    "number": {
      -      "title": "Number",
      -      "type": "number"
      -    },
      -    "result": {
      -      "title": "Result",
      -      "type": "number"
      -    }
      -  },
      -  "required": [
      -    "number",
      -    "result"
      -  ],
      -  "title": "CubeResponse",
      -  "type": "object"
      -}
    • addedOutput schema / $defs / app__routers__math_utils__CubeResponse
      Added value: +{
      +  "properties": {
      +    "number": {
      +      "title": "Number",
      +      "type": "number"
      +    },
      +    "result": {
      +      "title": "Result",
      +      "type": "number"
      +    }
      +  },
      +  "required": [
      +    "number",
      +    "result"
      +  ],
      +  "title": "CubeResponse",
      +  "type": "object"
      +}
    • changedOutput schema / x-fastmcp-top-level-schema
      Previous value: -"CubeResponse"New value: +"app__routers__math_utils__CubeResponse"
  4. Changed3 schema fields changed
    • addedOutput schema / $defs / CubeResponse
      Added value: +{
      +  "properties": {
      +    "number": {
      +      "title": "Number",
      +      "type": "number"
      +    },
      +    "result": {
      +      "title": "Result",
      +      "type": "number"
      +    }
      +  },
      +  "required": [
      +    "number",
      +    "result"
      +  ],
      +  "title": "CubeResponse",
      +  "type": "object"
      +}
    • removedOutput schema / $defs / app__routers__math_utils__CubeResponse
      Removed value: -{
      -  "properties": {
      -    "number": {
      -      "title": "Number",
      -      "type": "number"
      -    },
      -    "result": {
      -      "title": "Result",
      -      "type": "number"
      -    }
      -  },
      -  "required": [
      -    "number",
      -    "result"
      -  ],
      -  "title": "CubeResponse",
      -  "type": "object"
      -}
    • changedOutput schema / x-fastmcp-top-level-schema
      Previous value: -"app__routers__math_utils__CubeResponse"New value: +"CubeResponse"
  5. Changed3 schema fields changed
    • removedOutput schema / $defs / CubeResponse
      Removed value: -{
      -  "properties": {
      -    "number": {
      -      "title": "Number",
      -      "type": "number"
      -    },
      -    "result": {
      -      "title": "Result",
      -      "type": "number"
      -    }
      -  },
      -  "required": [
      -    "number",
      -    "result"
      -  ],
      -  "title": "CubeResponse",
      -  "type": "object"
      -}
    • addedOutput schema / $defs / app__routers__math_utils__CubeResponse
      Added value: +{
      +  "properties": {
      +    "number": {
      +      "title": "Number",
      +      "type": "number"
      +    },
      +    "result": {
      +      "title": "Result",
      +      "type": "number"
      +    }
      +  },
      +  "required": [
      +    "number",
      +    "result"
      +  ],
      +  "title": "CubeResponse",
      +  "type": "object"
      +}
    • changedOutput schema / x-fastmcp-top-level-schema
      Previous value: -"CubeResponse"New value: +"app__routers__math_utils__CubeResponse"
  6. Changed3 schema fields changed
    • addedOutput schema / $defs / CubeResponse
      Added value: +{
      +  "properties": {
      +    "number": {
      +      "title": "Number",
      +      "type": "number"
      +    },
      +    "result": {
      +      "title": "Result",
      +      "type": "number"
      +    }
      +  },
      +  "required": [
      +    "number",
      +    "result"
      +  ],
      +  "title": "CubeResponse",
      +  "type": "object"
      +}
    • removedOutput schema / $defs / app__routers__math_utils__CubeResponse
      Removed value: -{
      -  "properties": {
      -    "number": {
      -      "title": "Number",
      -      "type": "number"
      -    },
      -    "result": {
      -      "title": "Result",
      -      "type": "number"
      -    }
      -  },
      -  "required": [
      -    "number",
      -    "result"
      -  ],
      -  "title": "CubeResponse",
      -  "type": "object"
      -}
    • changedOutput schema / x-fastmcp-top-level-schema
      Previous value: -"app__routers__math_utils__CubeResponse"New value: +"CubeResponse"
  7. 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 carries the burden, but for a pure deterministic math function the risk surface is minimal. It does not state how negative numbers or non-integers are handled, though the presence of an output schema reduces the need to describe return values.

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?

A single short sentence that is front-loaded with the verb and resource. For a one-parameter arithmetic tool, nothing more is needed and there is no wasted text.

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?

With one required parameter, full schema coverage, and an output schema defining the return value, the description is sufficient to call the tool correctly. It could mention input domain or sibling distinctions, but those are minor for a trivial computation.

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 single parameter 'number' is fully documented as 'Number to cube'. The description adds no syntax or format detail beyond the schema, so the baseline 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 states a specific verb and resource (calculate the cube of a number), so an agent knows exactly what computation is performed. It does not differentiate itself from near-siblings such as square, nth_cube, or power, leaving that distinction to the name alone.

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?

There is no guidance on when to use this tool versus square, nth_cube, power, or cube_root. Usage is only implied by the name and the obvious mathematical semantics; no alternatives or exclusions are mentioned.

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.