Skip to main content
Glama

sha512

Compute SHA-512 hash of an input string for cryptographic verification and data integrity validation.

Instructions

Calculate SHA-512 hash of a string

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
inputYesThe input string to hash

Implementation Reference

  • DigestUtil.sha512() - The core handler that computes SHA-512 hash using CryptoJS.SHA512() and returns the result as a hex string.
    /**
     * Calculate SHA-512 hash of a string
     * @param input The input string to hash
     * @returns 128-character hexadecimal SHA-512 hash
     */
    static sha512(input: string): string {
      const hash = CryptoJS.SHA512(input);
      return hash.toString();
    }
  • Registration of the 'sha512' tool on the McpServer, with a Zod schema for input validation and a handler that delegates to DigestUtil.sha512().
    // Register SHA-512 tool
    server.tool(
      "sha512",
      "Calculate SHA-512 hash of a string",
      {
        input: z.string().describe("The input string to hash"),
      },
      ({ input }) => {
        const hash = DigestUtil.sha512(input);
        return {
          content: [{ type: "text", text: hash }],
        };
      }
    );
  • Zod schema defining the 'input' parameter as a required string for the sha512 tool.
    {
      input: z.string().describe("The input string to hash"),
  • src/index.ts:16-16 (registration)
    Top-level registration call that registers the digest tool (including sha512) on the MCP server.
    registerDigestTool(server);
Behavior2/5

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

No annotations exist; the description only says 'calculate hash' without specifying output format (e.g., hex string, base64) or behavior on edge cases like empty input.

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?

A single, direct sentence with no superfluous content, efficiently conveying the tool's purpose.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple hash tool with one parameter and no output schema, the description is minimally adequate but lacks details on output representation.

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?

The schema already explains the single parameter at 100% coverage; the description adds no additional meaning beyond what the schema provides.

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 action (calculate) and the specific algorithm (SHA-512) on a string input, distinguishing it from sibling hash functions and other crypto tools.

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 guidance on when to use SHA-512 over alternatives like sha256 or sha384, nor any contextual hints about appropriate 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/1595901624/crypto-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server