Skip to main content
Glama
islobodan

Crucher MCP

percentage_reverse

Read-onlyIdempotent

Find the total value from a known part and its percentage. Example: 30 is 15% of what number?

Instructions

X is Y% of what? e.g., 30 is 15% of 200

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
valueYes
percentYes

Implementation Reference

  • Schema definition for percentage_reverse tool: inputSchema with 'value' (number) and 'percent' (number), both required. Description: 'X is Y% of what? e.g., 30 is 15% of 200'.
    {
        name: "percentage_reverse",
        annotations: {
            title: "Percentage Reverse",
            readOnlyHint: true,
            destructiveHint: false,
            idempotentHint: true,
            openWorldHint: false,
        },
        description:
            "X is Y% of what? e.g., 30 is 15% of 200",
        inputSchema: {
            type: "object",
            properties: {
                value: { type: "number" },
                percent: { type: "number" },
            },
            required: ["value", "percent"],
        },
    },
  • Handler implementation for percentage_reverse tool. Takes {value, percent} and returns (value / percent) * 100. Throws error if percent is zero.
    percentage_reverse: ({ value, percent }) => {
        // X is Y% of what: (X / Y) * 100
        if (percent === 0)
            throw new Error("Cannot reverse percentage with zero percent.");
        return (value / percent) * 100;
    },
  • cruncher.js:77-78 (registration)
    Tool name 'percentage_reverse' registered in the 'standard' tool tier set (line 77) and also appears in the 'full' tier set.
    "percentage_of", "percentage_change", "percentage_reverse",
    "median", "range",
  • cruncher.js:139-141 (registration)
    Additional registration: 'percentage_reverse' marked as a MAIN_THREAD_TOOLS (line 140), meaning it runs in the main thread without worker overhead.
    // Percentage
    "percentage_of", "percentage_change", "percentage_reverse",
    // Math one-liners
Behavior3/5

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

Annotations already declare readOnlyHint, destructiveHint, and idempotentHint, covering the safety profile. The description adds no further behavioral context beyond the purpose.

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 extremely concise, consisting of a single sentence and an example, which is appropriate for a simple math tool.

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 the simplicity of the tool, good annotations, and no output schema, the description is mostly adequate. However, missing parameter documentation reduces completeness slightly.

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

Parameters2/5

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

Schema parameter descriptions are absent (0% coverage) and the description does not explain the meaning of 'value' or 'percent' individually. The example hints at their roles but is insufficient for full understanding.

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 a base value given a part and percentage, and the example solidifies the purpose. It distinguishes itself from sibling percentage tools like percentage_of and percentage_change.

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 through the example but provides no explicit guidance on when to use this tool versus alternatives, nor when-not-to-use conditions.

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