Skip to main content
Glama
islobodan

Crucher MCP

power

Read-onlyIdempotent

Raise a number to an exponent. Provide the base and exponent to compute the result.

Instructions

Raises a to the power of b.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
baseYes
exponentYes

Implementation Reference

  • The handler function for the 'power' tool. It takes 'base' and 'exponent' arguments and returns Math.pow(base, exponent).
    /**
     * Calculates a number raised to a power.
     * @param {Object} args - The arguments object.
     * @param {number} args.base - The base number.
     * @param {number} args.exponent - The exponent.
     * @returns {number} The result of base raised to the power of exponent.
     */
    power: ({ base, exponent }) => Math.pow(base, exponent),
Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already declare readOnlyHint, destructiveHint, and idempotentHint, so the safety profile is clear. The description adds no additional behavioral context, but it does not contradict annotations and the tool is trivially simple.

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, concise sentence that conveys the entire purpose without any unnecessary 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.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool's simplicity (two numeric inputs, no output schema, no side effects), the description provides complete information needed for correct invocation.

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?

Parameter names 'base' and 'exponent' are self-explanatory, and the description maps 'a' and 'b' to them. Despite 0% schema description coverage, the meaning is clear without extra detail.

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 'Raises a to the power of b.' uses a specific verb ('raises') and resource (power operation), clearly distinguishing it from sibling tools like add, multiply, or sqrt.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No explicit when-to-use or alternative guidance is provided. However, for a fundamental mathematical operation, the purpose is self-evident, so a middle score is appropriate.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/islobodan/cruncher-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server