Skip to main content
Glama

sha384

Convert any input string into a SHA-384 hash to produce a fixed-size, cryptographically secure digest for data integrity verification.

Instructions

Calculate SHA-384 hash of a string

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
inputYesThe input string to hash

Implementation Reference

  • Static method that computes SHA-384 hash using CryptoJS.SHA384 and returns the hex string.
    static sha384(input: string): string {
      const hash = CryptoJS.SHA384(input);
      return hash.toString();
    }
  • Registers the 'sha384' tool on the MCP server with a Zod schema for input validation.
    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 }],
        };
      }
    );
  • Zod schema defining the single required input parameter (a string) for the sha384 tool.
    {
      input: z.string().describe("The input string to hash"),
    },
Behavior2/5

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

No annotations; description only states the action without detailing output format, encoding, or side effects beyond calculation.

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 concise sentence, front-loaded with action and resource, no redundancy.

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?

Lacks output specification (e.g., hex string) and any usage hints; adequate for a simple tool but incomplete without examples.

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?

Schema coverage is 100% with parameter description; tool 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?

Clear verb 'Calculate' and specific resource 'SHA-384 hash of a string' distinguishes it from sibling hash 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-384 versus other hash algorithms, no security or performance context.

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