Skip to main content
Glama
islobodan

Crucher MCP

get_angle_mode

Read-onlyIdempotent

Retrieve the current trigonometric angle mode (degrees or radians) used by the calculator. Ensures correct interpretation of angle values in subsequent calculations.

Instructions

Get current trig angle mode.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • Handler function for get_angle_mode tool. Returns the current global angle mode (degrees or radians) as a JSON-stringified object.
    /** Get the current global angle mode. */
    get_angle_mode: () => {
        return JSON.stringify({ mode: angleMode });
    },
  • Input schema definition for get_angle_mode tool. Has no required properties (no inputs needed) and returns the current trig angle mode.
    {
        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:81-81 (registration)
    Registration of get_angle_mode in the 'standard' tool tier, making it available when CRUNCHER_TOOL_SET is 'standard' (default).
    "set_angle_mode", "get_angle_mode",
  • cruncher.js:138-138 (registration)
    get_angle_mode is listed in MAIN_THREAD_TOOLS set, meaning it runs directly in the main thread without worker overhead.
    "set_angle_mode", "get_angle_mode",
  • Global angleMode state variable initialized to 'degrees', used by get_angle_mode handler.
    // --- Angle Mode State ---
    let angleMode = "degrees"; // Default unit for trigonometric functions
Behavior2/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false. The description adds no behavioral context beyond the name, such as the return format or side effects. With annotations present, the bar is lower, but description still misses opportunity to clarify what 'angle mode' means.

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?

The description is a single, front-loaded sentence with no extraneous words. It efficiently conveys the tool's purpose.

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 zero parameters, no output schema, and simple purpose, the description is complete. An agent can infer what the tool returns based on the name and description.

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?

There are no parameters (100% schema coverage). The description does not need to explain parameters. Baseline 4 is appropriate as no additional info is required.

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 'Get current trig angle mode' clearly states the tool's action (get) and resource (current trig angle mode). It distinguishes from sibling 'set_angle_mode' by being a read-only counterpart.

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?

The description implies usage when needing to know the current angle mode, but does not explicitly state when to use or provide alternatives. Given it's a simple getter, no further guidance is critical.

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