Skip to main content
Glama

security-crypto

aes_gcm_encrypt_decrypt

Authenticated AES-256-GCM encryption and decryption using Node crypto with random 96-bit IVs and 128-bit GCM auth tags.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "aes_gcm_encrypt_decrypt"
  }
}

Input Schema

NameRequiredDescriptionDefault
modeNoencrypt
textNo
ivHexNo
keyHexNo
authTagHexNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.9/5.0
Behavior3/5

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

With no annotations, the description carries the full burden, and it does add real behavioral facts: 96-bit random IVs and 128-bit GCM auth tags, which implies the IV is generated on encrypt and a tag is produced. It omits error/verification behavior on tag mismatch, permission or key-handling requirements, and any return shape.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single front-loaded sentence with no filler; the algorithm and its security-relevant parameters come first. It is efficient, though its brevity is part of why semantics are thin.

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

Completeness2/5

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

For a 5-parameter cryptographic tool with no annotations, no output schema, and no schema descriptions, the definition is too sparse: an agent cannot tell which parameters are required per mode, what is returned, or how failures surface.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 0% across 5 parameters, so the description must compensate. It indirectly clarifies hex encoding and byte sizes for ivHex (12 bytes) and authTagHex (16 bytes), but says nothing about mode, text encoding, keyHex requirements, or which parameters are conditional on mode.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb pair (encrypt/decrypt) and algorithm (AES-256-GCM), plus implementation detail (Node crypto) that separates it from sibling crypto tools like hmac_sign_and_verify or password_kdf_hash_and_verify. It never explicitly names when a sibling is preferred, but the algorithm specificity makes the tool's identity 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?

No guidance on when to use this rather than the sibling HMAC/KDF tools, and no prerequisites. It also doesn't say which mode to pick or that decryption requires a caller-supplied ivHex and authTagHex while encryption generates the IV itself.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources