Skip to main content
Glama
Sign In
Kratos-MCP

Kratos-MCP

by FoggyStorm
OverviewSchemaRelated ServersDiscussionsAdmin
TypeScript
Hybrid

security_encrypt

Encrypt sensitive data for secure storage using a tool integrated with Kratos-MCP, a memory system for AI coding tools that ensures data protection and traceability.

Instructions

Encrypt sensitive data for storage

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": {
      "data": "<data>"
    },
    "name": "security_encrypt"
  }
}

Input Schema

NameRequiredDescriptionDefault
dataYesData to encrypt

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.9/5.0
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 mentions encryption for storage but fails to detail critical aspects like encryption algorithms, key management, performance impact, or error handling. This leaves significant gaps for a security-related tool.

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 that directly states the tool's purpose without any fluff. It is appropriately sized and front-loaded, making it easy to understand at a glance.

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?

Given the complexity of encryption operations and the lack of annotations and output schema, the description is insufficient. It doesn't cover return values, error cases, or security implications, leaving the agent with incomplete information for safe and effective use.

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 parameter 'data' documented as 'Data to encrypt'. The description adds no additional meaning beyond this, such as format examples or constraints. Since the schema does the heavy lifting, a baseline score of 3 is appropriate.

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?

The description clearly states the verb ('encrypt') and resource ('sensitive data'), and specifies the purpose ('for storage'), making the tool's function unambiguous. However, it doesn't differentiate from sibling tools like 'security_gdpr_export' or 'security_scan', which prevents a perfect score.

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 (e.g., 'security_gdpr_export' for data export or 'security_scan' for scanning). It lacks context about prerequisites, such as when encryption is needed over other security measures, leaving usage unclear.

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

Deploy Server

Other Tools

Related Tools