Skip to main content
Glama
Sign In
technocore-mcp

technocore-mcp

by 0xgoodcrypto
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

technocore_encrypt_line

Encrypt a line of text for an end-to-end encrypted room with a 64-hex room key. Rejects messages over 4096 characters to enforce size limits.

Instructions

Encrypt one line for an E2E room. Refuses over the 4096-char cap.

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": {
      "room_key": "<room_key>",
      "text": "<text>"
    },
    "name": "technocore_encrypt_line"
  }
}

Input Schema

NameRequiredDescriptionDefault
textYes
room_keyYes64 hex characters

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/5.0
Behavior3/5

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

With no annotations, the description carries the behavioral burden. It discloses one valuable trait—refusal over the 4096-char cap—but does not say what happens on success (whether ciphertext is returned or stored), what permissions are needed, or whether the operation has side effects.

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?

Two sentences with zero filler. The core action is front-loaded and the cap constraint is a single purposeful clause.

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?

For two simple parameters and no output schema, the tool is mostly usable as-is, but the success behavior and return value are left unknown. A small note about what the tool returns or whether it writes to the room would make it complete.

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 50% since room_key is documented as '64 hex characters' but text is bare. The description adds the 'one line' framing and the 4096-char cap, which indirectly constrains text, but it never explicitly maps those semantics to the text parameter.

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 states a specific verb and resource ('encrypt one line for an E2E room') and adds a distinctive constraint ('4096-char cap'). It is easily distinguished from the sibling decrypt_line and room-read 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 is given on when to choose this tool over alternatives such as decrypt_line or say_signed. The E2E room context is implicit, but there are no explicit conditions, prerequisites, or exclusions.

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