Skip to main content
Glama
islobodan

Crucher MCP

sine

Read-onlyIdempotent

Compute the sine of an angle, using degrees by default or radians when specified. Returns the trigonometric sine value.

Instructions

Sine. Angle in degrees by default, or radians with unit: "radians".

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
angleYes
unitNo

Implementation Reference

  • Schema definition for the 'sine' tool: accepts an angle number and optional unit (degrees/radians), angle is required.
    {
        name: "sine",
        annotations: {
            title: "Sine",
            readOnlyHint: true,
            destructiveHint: false,
            idempotentHint: true,
            openWorldHint: false,
        },
        description:
            'Sine. Angle in degrees by default, or radians with unit: "radians".',
        inputSchema: {
            type: "object",
            properties: {
                angle: { type: "number" },
                unit: { type: "string", enum: ["degrees", "radians"] },
            },
            required: ["angle"],
        },
    },
  • Handler implementation for the 'sine' tool: converts the angle to radians via toRadians() (using the global angleMode or provided unit), then calls Math.sin().
    sine: ({ angle, unit }) => Math.sin(toRadians(angle, unit)),
  • Helper function toRadians that converts degrees to radians, using global angleMode if no unit is specified.
    const toRadians = (angle, unit) => {
        const resolved = unit || angleMode;
        return resolved === "degrees" ? angle * (Math.PI / 180) : angle;
    };
  • cruncher.js:69-80 (registration)
    Tool tier registration: 'sine' is listed in the 'standard' tool set (34 tools), making it available by default.
    standard: [
        "evaluate_expression",
        "add", "subtract", "multiply", "divide",
        "sqrt", "power", "absolute", "modulo", "factorial",
        "logarithm", "natural_log", "get_constant",
        "sine", "cosine", "tangent", "asin", "acos", "atan",
        "set_angle_mode", "get_angle_mode",
        "sum", "avg", "min", "max", "count", "variance", "std_dev",
        "percentage_of", "percentage_change", "percentage_reverse",
        "median", "range",
        "convert_unit",
    ],
  • cruncher.js:130-134 (registration)
    MAIN_THREAD_TOOLS set includes 'sine', meaning it runs directly in the main thread without spawning a worker.
    const MAIN_THREAD_TOOLS = new Set([
        // Angle management
        "set_angle_mode", "get_angle_mode",
        // Trigonometry (instant Math calls)
        "sine", "cosine", "tangent", "asin", "acos", "atan",
Behavior4/5

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

Annotations already mark readOnlyHint=true and idempotentHint=true. The description adds value by explaining unit handling and default behavior, which is not captured in annotations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single, efficient sentence. It is front-loaded and clear. Slightly more structured formatting could improve scannability, but it is concise.

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?

For a simple mathematical tool with no output schema and good annotations, the description covers the essential unit behavior. It is complete enough for correct invocation.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description must compensate. It explains the 'angle' parameter and the 'unit' parameter with its enum and default behavior, adding meaning beyond the raw schema.

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 clearly states the tool computes the sine of an angle, with unit handling. It distinguishes from sibling sine-like tools (e.g., cosine, tangent) and specifies the default unit (degrees) and optional radians.

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 when-not-to-use guidance, but the function is well-known. The description implies default unit behavior but does not clarify when to choose radians over degrees. Adequate for a simple math tool.

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