Skip to main content
Glama

sha224

Calculate the SHA-224 hash of any input string using the Crypto_MCP server. Provides a cryptographic hash output for data integrity verification.

Instructions

Calculate SHA-224 hash of a string

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
inputYesThe input string to hash

Implementation Reference

  • The sha224 static method on DigestUtil that computes SHA-224 hash using CryptoJS.SHA224
    /**
     * Calculate SHA-224 hash of a string
     * @param input The input string to hash
     * @returns 56-character hexadecimal SHA-224 hash
     */
    static sha224(input: string): string {
      const hash = CryptoJS.SHA224(input);
      return hash.toString();
    }
  • Zod schema for the sha224 tool input - a single string parameter named 'input'
    "Calculate SHA-224 hash of a string",
    {
      input: z.string().describe("The input string to hash"),
  • Registration of the 'sha224' tool on the McpServer via server.tool()
    // Register SHA-224 tool
    server.tool(
      "sha224",
      "Calculate SHA-224 hash of a string",
      {
        input: z.string().describe("The input string to hash"),
      },
      ({ input }) => {
        const hash = DigestUtil.sha224(input);
        return {
          content: [{ type: "text", text: hash }],
        };
      }
    );
Behavior2/5

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

No annotations are present, so the description must carry the full burden. It only states 'calculate hash' without detailing deterministic nature, output format (e.g., hex string), or side effects. This is minimal disclosure for a one-way cryptographic operation.

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 redundant words. Every word is necessary for the basic purpose.

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 tool's simplicity (one parameter, no output schema), the description is largely complete. It misses an explicit note that the output is a hex string, but this is implied by 'hash'. Sibling tools have similar minimal descriptions.

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 the parameter described as 'The input string to hash'. The description adds no new meaning beyond the schema, so baseline 3 is appropriate.

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 verb 'calculate' and the specific resource 'SHA-224 hash', which distinguishes it from sibling tools like md5, sha1, sha256, etc. It is precise and unambiguous.

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 SHA-224 versus other hash algorithms (e.g., SHA-256, MD5). It lacks context about security levels or compatibility, leaving the agent without decision-making support.

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