Skip to main content
Glama
OOBE-PROTOCOL

SAP MCP Server

sap_compact_inscribe_memory

Inscribe encrypted memory data into a Solana vault by providing session PDA, vault PDA, encrypted data, nonce, and content hash.

Instructions

Compact memory inscription with explicit vault/session PDAs.

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
Behavior2/5

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

With no annotations, the description must disclose behavioral traits. It only mentions 'compact' and 'explicit PDAs', but does not describe side effects, authorization needs, error conditions, or what gets modified.

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

Conciseness3/5

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

The description is a single sentence, which is concise but lacks necessary detail. It is front-loaded with the key action, but could benefit from expanding to cover usage and behavior.

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 5 parameters, no output schema, and no annotations, the description is too brief. It does not explain what 'compact' entails, the role of explicit PDAs, or any constraints. The tool likely requires more context for correct usage.

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?

All 5 parameters have descriptions in the input schema, achieving 100% schema coverage. The tool description adds no additional meaning beyond what the schema already provides, meeting the baseline.

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 identifies the tool as a memory inscription action, specifying it is 'compact' and uses 'explicit vault/session PDAs'. This distinguishes it from sibling 'sap_inscribe_memory', but the term 'compact' is not explained.

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 provided on when to use this tool versus alternatives like 'sap_inscribe_memory'. There are no explicit conditions, exclusions, or references to other tools.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/OOBE-PROTOCOL/sap-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server