Skip to main content
Glama

TinyFn

nth_cube

Get the nth cube 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": {
      "n": "<n>"
    },
    "name": "nth_cube"
  }
}

Input Schema

NameRequiredDescriptionDefault
nYesWhich cube number

Output Schema

NameRequiredDescriptionDefault
nYes
cubeYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • addedOutput schema / $defs / CubeResponse
      Added value: +{
      +  "properties": {
      +    "cube": {
      +      "title": "Cube",
      +      "type": "integer"
      +    },
      +    "n": {
      +      "title": "N",
      +      "type": "integer"
      +    }
      +  },
      +  "required": [
      +    "n",
      +    "cube"
      +  ],
      +  "title": "CubeResponse",
      +  "type": "object"
      +}
    • removedOutput schema / $defs / app__routers__number_utils__CubeResponse
      Removed value: -{
      -  "properties": {
      -    "cube": {
      -      "title": "Cube",
      -      "type": "integer"
      -    },
      -    "n": {
      -      "title": "N",
      -      "type": "integer"
      -    }
      -  },
      -  "required": [
      -    "n",
      -    "cube"
      -  ],
      -  "title": "CubeResponse",
      -  "type": "object"
      -}
    • changedOutput schema / x-fastmcp-top-level-schema
      Previous value: -"app__routers__number_utils__CubeResponse"New value: +"CubeResponse"
  2. Changed3 schema fields changed
    • removedOutput schema / $defs / CubeResponse
      Removed value: -{
      -  "properties": {
      -    "cube": {
      -      "title": "Cube",
      -      "type": "integer"
      -    },
      -    "n": {
      -      "title": "N",
      -      "type": "integer"
      -    }
      -  },
      -  "required": [
      -    "n",
      -    "cube"
      -  ],
      -  "title": "CubeResponse",
      -  "type": "object"
      -}
    • addedOutput schema / $defs / app__routers__number_utils__CubeResponse
      Added value: +{
      +  "properties": {
      +    "cube": {
      +      "title": "Cube",
      +      "type": "integer"
      +    },
      +    "n": {
      +      "title": "N",
      +      "type": "integer"
      +    }
      +  },
      +  "required": [
      +    "n",
      +    "cube"
      +  ],
      +  "title": "CubeResponse",
      +  "type": "object"
      +}
    • changedOutput schema / x-fastmcp-top-level-schema
      Previous value: -"CubeResponse"New value: +"app__routers__number_utils__CubeResponse"
  3. Changed3 schema fields changed
    • addedOutput schema / $defs / CubeResponse
      Added value: +{
      +  "properties": {
      +    "cube": {
      +      "title": "Cube",
      +      "type": "integer"
      +    },
      +    "n": {
      +      "title": "N",
      +      "type": "integer"
      +    }
      +  },
      +  "required": [
      +    "n",
      +    "cube"
      +  ],
      +  "title": "CubeResponse",
      +  "type": "object"
      +}
    • removedOutput schema / $defs / app__routers__number_utils__CubeResponse
      Removed value: -{
      -  "properties": {
      -    "cube": {
      -      "title": "Cube",
      -      "type": "integer"
      -    },
      -    "n": {
      -      "title": "N",
      -      "type": "integer"
      -    }
      -  },
      -  "required": [
      -    "n",
      -    "cube"
      -  ],
      -  "title": "CubeResponse",
      -  "type": "object"
      -}
    • changedOutput schema / x-fastmcp-top-level-schema
      Previous value: -"app__routers__number_utils__CubeResponse"New value: +"CubeResponse"
  4. Changed3 schema fields changed
    • removedOutput schema / $defs / CubeResponse
      Removed value: -{
      -  "properties": {
      -    "cube": {
      -      "title": "Cube",
      -      "type": "integer"
      -    },
      -    "n": {
      -      "title": "N",
      -      "type": "integer"
      -    }
      -  },
      -  "required": [
      -    "n",
      -    "cube"
      -  ],
      -  "title": "CubeResponse",
      -  "type": "object"
      -}
    • addedOutput schema / $defs / app__routers__number_utils__CubeResponse
      Added value: +{
      +  "properties": {
      +    "cube": {
      +      "title": "Cube",
      +      "type": "integer"
      +    },
      +    "n": {
      +      "title": "N",
      +      "type": "integer"
      +    }
      +  },
      +  "required": [
      +    "n",
      +    "cube"
      +  ],
      +  "title": "CubeResponse",
      +  "type": "object"
      +}
    • changedOutput schema / x-fastmcp-top-level-schema
      Previous value: -"CubeResponse"New value: +"app__routers__number_utils__CubeResponse"
  5. Changed3 schema fields changed
    • addedOutput schema / $defs / CubeResponse
      Added value: +{
      +  "properties": {
      +    "cube": {
      +      "title": "Cube",
      +      "type": "integer"
      +    },
      +    "n": {
      +      "title": "N",
      +      "type": "integer"
      +    }
      +  },
      +  "required": [
      +    "n",
      +    "cube"
      +  ],
      +  "title": "CubeResponse",
      +  "type": "object"
      +}
    • removedOutput schema / $defs / app__routers__number_utils__CubeResponse
      Removed value: -{
      -  "properties": {
      -    "cube": {
      -      "title": "Cube",
      -      "type": "integer"
      -    },
      -    "n": {
      -      "title": "N",
      -      "type": "integer"
      -    }
      -  },
      -  "required": [
      -    "n",
      -    "cube"
      -  ],
      -  "title": "CubeResponse",
      -  "type": "object"
      -}
    • changedOutput schema / x-fastmcp-top-level-schema
      Previous value: -"app__routers__number_utils__CubeResponse"New value: +"CubeResponse"
  6. Changed3 schema fields changed
    • removedOutput schema / $defs / CubeResponse
      Removed value: -{
      -  "properties": {
      -    "cube": {
      -      "title": "Cube",
      -      "type": "integer"
      -    },
      -    "n": {
      -      "title": "N",
      -      "type": "integer"
      -    }
      -  },
      -  "required": [
      -    "n",
      -    "cube"
      -  ],
      -  "title": "CubeResponse",
      -  "type": "object"
      -}
    • addedOutput schema / $defs / app__routers__number_utils__CubeResponse
      Added value: +{
      +  "properties": {
      +    "cube": {
      +      "title": "Cube",
      +      "type": "integer"
      +    },
      +    "n": {
      +      "title": "N",
      +      "type": "integer"
      +    }
      +  },
      +  "required": [
      +    "n",
      +    "cube"
      +  ],
      +  "title": "CubeResponse",
      +  "type": "object"
      +}
    • changedOutput schema / x-fastmcp-top-level-schema
      Previous value: -"CubeResponse"New value: +"app__routers__number_utils__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 exist, so the description carries full burden, but for a pure, side-effect-free arithmetic function the risk surface is minimal. It does not state that input is validated against 1..10000 or what happens outside that range, leaving a small but real gap.

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?

One short, front-loaded sentence with no filler; nothing could be removed without losing meaning.

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 well-bounded parameter and an existing output schema, the description is nearly sufficient for correct invocation. The only omission is disambiguation from the closely related `cube` sibling.

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 `n` is documented with bounds (1 to 10000) in the schema. The description adds no meaning beyond 'Which cube number', so the baseline of 3 applies.

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?

States a specific verb and resource ('Get the nth cube number'), which is unambiguous in isolation. However, it does not differentiate from the sibling `cube` (and near-neighbors like `nth_square`, `nth_prime`), so an agent cannot tell why both exist.

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 versus `cube` or `power`, nor any exclusion of out-of-range inputs. Usage is only implied by the name.

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.