Skip to main content
Glama
islobodan

Crucher MCP

get_angle_mode

Read-onlyIdempotent

Retrieve the current trigonometric angle mode setting for calculations. Identifies whether angle inputs are interpreted as degrees or radians.

Instructions

Get current trig angle mode.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • Schema definition for the get_angle_mode tool: name, annotations, description, and inputSchema (empty object with no required params).
    {
        name: "get_angle_mode",
        annotations: {
            title: "Get Angle Mode",
            readOnlyHint: true,
            destructiveHint: false,
            idempotentHint: true,
            openWorldHint: false,
        },
        description: "Get current trig angle mode.",
        inputSchema: { type: "object", properties: {}, required: [] }
    },
  • cruncher.js:130-133 (registration)
    Registration of get_angle_mode in MAIN_THREAD_TOOLS set, marking it as an instant tool that runs in the main thread (no worker overhead).
    const MAIN_THREAD_TOOLS = new Set([
        // Angle management
        "set_angle_mode", "get_angle_mode",
        // Trigonometry (instant Math calls)
  • cruncher.js:75-76 (registration)
    Registration in the 'standard' tool tier — get_angle_mode is available in both standard and full tool sets.
    "set_angle_mode", "get_angle_mode",
    "sum", "avg", "min", "max", "count", "variance", "std_dev",
  • Handler function for get_angle_mode — returns the current global angle mode as a JSON string containing the 'mode' property (either 'degrees' or 'radians').
    /** Get the current global angle mode. */
    get_angle_mode: () => {
        return JSON.stringify({ mode: angleMode });
    },
  • Global state variable 'angleMode' that get_angle_mode reads from. Initialized to 'degrees' by default.
    // --- Angle Mode State ---
    let angleMode = "degrees"; // Default unit for trigonometric functions
Behavior4/5

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

Annotations already declare readOnlyHint, destructiveHint, and idempotentHint as true, false, true respectively. Description states 'Get current trig angle mode', which is consistent and adds minimal extra context. No contradiction.

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?

Single, efficient sentence conveying the exact purpose with no extraneous words.

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?

Given simplicity (no params, no output schema), the description is almost complete. It lacks indication of the return format or possible values (e.g., 'degrees', 'radians'), but the overall context with sibling tools compensates.

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?

No parameters exist, so schema coverage is 100% by default. Description adds no param-specific information, but baseline for zero parameters is 4.

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 the action (Get) and resource (current trig angle mode). It is a specific verb+resource combination and implicitly distinguishes from sibling set_angle_mode.

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 guidance on when to use this tool versus alternatives like set_angle_mode. Usage is implied by the name but not elaborated.

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