Skip to main content
Glama
OOBE-PROTOCOL

SAP MCP Server

by OOBE-PROTOCOL
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Compact Inscribe SAP Memory

sap_compact_inscribe_memory

Inscribe compact memory with explicit vault and session PDAs, storing encrypted payloads or public hashes on-chain.

Instructions

Compact memory inscription with explicit vault/session PDAs. SAP MCP context: Memory/session flow. Store only intentionally encrypted payloads or public hashes; session and vault PDAs are visible on-chain metadata.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nonceNoEncryption nonce as a byte array, hex string, or base64 string
vaultPdaNoVault PDA (base58) for the memory inscription
sessionPdaNoSession PDA (base58) for the memory inscription
contentHashNo32-byte content hash as a byte array, hex string, or base64 string
encryptedDataNoEncrypted memory data as a byte array, hex string, or base64 string

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
contentYesMCP content blocks returned to the caller.
isErrorNoTrue when the tool result represents an application-level error.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.9.16
  2. Removedv0.9.6
  3. Changed1 schema field changedv0.7.4
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "properties": {
+    "content": {
+      "description": "MCP content blocks returned to the caller.",
+      "items": {
+        "properties": {
+          "text": {
+            "description": "Human-readable JSON or text returned by the tool.",
+            "type": "string"
+          },
+          "type": {
+            "description": "MCP content block type, usually text.",
+            "type": "string"
+          }
+        },
+        "required": [
+          "type"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "isError": {
+      "description": "True when the tool result represents an application-level error.",
+      "type": "boolean"
+    }
+  },
+  "required": [
+    "content"
+  ],
+  "type": "object"
+}
  4. Addedv0.6.0
  5. Removedv0.5.0
  6. First observedv0.1.0

TDQS

A3.9/5.0
Behavior4/5

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

Adds important behavioral context beyond annotations: warns that 'session and vault PDAs are visible on-chain metadata' and clarifies what data should be stored. Annotations (readOnlyHint=false, openWorldHint=true) are consistent, and description provides extra safety guidance.

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: first states purpose, second gives context and warning. No filler, front-loaded, efficient for an agent to parse.

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?

Adequate for a tool with output schema and annotations. However, the concept of 'inscribe memory' might be unclear without additional context about the SAP protocol. Sibling 'sap_inscribe_memory' could provide more, but this description alone is somewhat minimal.

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 descriptions for all 5 parameters. The description does not add per-parameter details beyond the schema, but provides an overarching security note. 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 tool's purpose: 'Compact memory inscription with explicit vault/session PDAs.' It specifies the resource (memory) and action (inscribe) and distinguishes from sibling 'sap_inscribe_memory' by being 'compact' and requiring explicit PDAs.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Provides context: 'SAP MCP context: Memory/session flow' and a guideline: 'Store only intentionally encrypted payloads or public hashes.' However, it does not explicitly state when not to use this tool or mention alternatives like 'sap_inscribe_memory'.

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