Skip to main content
Glama
islobodan

Crucher MCP

atan

Read-onlyIdempotent

Compute the arctangent of a number. Returns result in degrees by default, or radians when specified.

Instructions

Arctangent. Result in degrees by default, or radians with unit param.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
valueYes
unitNo

Implementation Reference

  • Tool definition schema for 'atan' - defines input parameters (value: number, unit: enum degrees/radians), required value, and description.
    {
        name: "atan",
        annotations: {
            title: "Arctangent",
            readOnlyHint: true,
            destructiveHint: false,
            idempotentHint: true,
            openWorldHint: false,
        },
        description:
            'Arctangent. Result in degrees by default, or radians with unit param.',
        inputSchema: {
            type: "object",
            properties: {
                value: { type: "number" },
                unit: { type: "string", enum: ["degrees", "radians"] },
            },
            required: ["value"],
        },
    },
  • Handler implementation for 'atan' - computes arctangent using Math.atan() and converts the result from radians to the specified unit (degrees/radians) using fromRadians helper.
    atan: ({ value, unit }) => fromRadians(Math.atan(value), unit),
  • cruncher.js:80-80 (registration)
    Tool registered in the 'standard' tool tier list, making it available when CRUNCHER_TOOL_SET is 'standard' or 'full'.
    "sine", "cosine", "tangent", "asin", "acos", "atan",
  • Helper function fromRadians used by atan handler to convert radian result to degrees (or keep radians) based on the unit parameter or global angleMode.
    const fromRadians = (radians, unit) => {
        const resolved = unit || angleMode;
        return resolved === "degrees" ? radians * (180 / Math.PI) : radians;
    };
  • 'atan' listed in MAIN_THREAD_TOOLS set, meaning it runs on the main thread (no worker overhead) for fast execution.
    "sine", "cosine", "tangent", "asin", "acos", "atan",
    // Cache management
Behavior4/5

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

Adds value beyond annotations by specifying default unit (degrees) and option for radians. Annotations already indicate readOnly, non-destructive, idempotent; description complements well.

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?

Two sentences, front-loaded key info, no redundancy. Efficient and clear.

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?

No output schema, but description implies result is an angle in specified units. Could explicitly mention return type, but sufficient for a simple math function given annotations.

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?

With 0% schema coverage, description partially compensates by explaining the 'unit' parameter. However, 'value' parameter lacks any description beyond the schema type.

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?

Description clearly states it computes arctangent, with unit specification. Differentiates from sibling trig functions like sine, cosine, tangent.

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 explicit guidance on when to use this tool vs alternatives. Does not mention inverse relationship to tangent or any use cases.

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