TextToolkit

by Cicatriiz

Overview Schema Source Related Servers Discussions Admin

TypeScript

Local

generate_hmac

Generate HMAC hashes from text using a secret key. Supports SHA256, SHA512, and MD5 algorithms.

Instructions

Generate HMAC hash

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "text": "<text>",
      "key": "<key>"
    },
    "name": "generate_hmac"
  }
}

Input Schema

Name	Required	Description	Default
`text`	Yes	The text to hash
`key`	Yes	The secret key for HMAC
`algorithm`	No	The hashing algorithm to use	SHA256

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Jun 21, 2026

TDQS

A3.6/5.0

Behavior3/5

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

With no annotations, the description carries full burden. 'Generate HMAC hash' accurately describes the core behavior but omits details like algorithm default, return format, or any side effects. Adequate but minimal.

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 sentence, front-loaded, no wasted words. Extremely concise.

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?

For a simple hash tool with no output schema, the description covers the essential purpose. Could be slightly more complete by hinting at key usage, but it's functional.

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 description coverage is 100%, so the description adds no extra meaning beyond the schema. 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 'Generate HMAC hash' clearly states the tool's action and resource. It distinguishes from sibling hash tools (e.g., generate_md5, generate_sha256) by specifying HMAC (keyed hashing).

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 this tool vs alternatives. Does not mention that HMAC requires a secret key, unlike other hash tools. No when-not-to-use or context provided.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.