Skip to main content
Glama

sha384

Calculate SHA-384 cryptographic hash for data integrity verification and security applications within the Crypto_MCP server environment.

Instructions

Calculate SHA-384 hash of a string

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
inputYesThe input string to hash

Implementation Reference

  • Handler function for the sha384 MCP tool. It invokes DigestUtil.sha384 on the input string and formats the result as MCP text content.
    ({ input }) => {
      const hash = DigestUtil.sha384(input);
      return {
        content: [{ type: "text", text: hash }],
      };
    }
  • Input schema definition for the sha384 tool using Zod, specifying a string parameter.
    {
      input: z.string().describe("The input string to hash"),
    },
  • Registration of the sha384 tool via server.tool call within registerDigestTool function.
    server.tool(
      "sha384",
      "Calculate SHA-384 hash of a string",
      {
        input: z.string().describe("The input string to hash"),
      },
      ({ input }) => {
        const hash = DigestUtil.sha384(input);
        return {
          content: [{ type: "text", text: hash }],
        };
      }
    );
  • Core implementation of SHA-384 hashing in DigestUtil class using CryptoJS library.
    static sha384(input: string): string {
      const hash = CryptoJS.SHA384(input);
      return hash.toString();
    }
  • src/index.ts:16-16 (registration)
    Top-level registration call that invokes registerDigestTool on the main McpServer instance, thereby registering the sha384 tool.
    registerDigestTool(server);
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It states the tool calculates a hash but doesn't mention whether it's deterministic, irreversible, or has any performance characteristics. While the purpose is clear, key behavioral traits like output format or error handling are omitted.

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, efficient sentence with zero wasted words. It's perfectly front-loaded and appropriately sized for a simple hashing function.

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 single-parameter tool with no annotations and no output schema, the description adequately states the core purpose. However, it lacks information about the return value format (hex, base64, etc.) and doesn't provide context about when to choose SHA-384 over other hash functions in the sibling set.

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 description coverage is 100%, with the single parameter 'input' fully documented in the schema. The description adds no additional parameter semantics beyond what's already in the schema, so it meets the baseline for high schema coverage.

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 specific action ('Calculate') and resource ('SHA-384 hash of a string'), distinguishing it from sibling tools like md5, sha1, sha256, etc. It precisely identifies the cryptographic hash function being used.

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?

The description provides no guidance on when to use this tool versus alternatives like sha256 or sha512, nor does it mention any prerequisites or constraints. It simply states what the tool does without contextual usage information.

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