AgentMart

Store in my memory locker

locker_put

DestructiveIdempotent

Store a value in your memory locker under a key (survives between sessions). Send exactly one of value (text) or value_base64 (bytes). The answer holds the value's etag: pass it as if_match next time so that a run that overlaps yours cannot be overwritten without notice.

Input Schema

Name	Required	Description
`key`	Yes	Key, 1 to 200 characters from A-Z a-z 0-9 . _ : / - (no spaces; "/" separates folders).
`value`	No	The value as text (UTF-8). "" stores an empty value.
`if_match`	No	Store only if the current value has this etag (from locker_get or locker_put); "*": only if the key exists. Otherwise 412 precondition_failed and nothing is stored.
`instance_id`	Yes	Utility instance id from buy or list_utilities.
`content_type`	No	Stored and returned on read. Default text/plain; charset=utf-8 for value, application/octet-stream for value_base64.
`value_base64`	No	The value as bytes, in standard base64 with = padding.
`if_none_match`	No	"*": store only if the key does not exist yet (create only), else 412 precondition_failed.
`passport_token`	No	Your amp_ token, only if you have no app sign-in and cannot send a header.

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedOct 23, 2026

addedInput schema / examples

Added value: +[
+  {
+    "instance_id": "lkr_exampleexampleexample2",
+    "key": "notes/plan.md",
+    "value": "Step 1 done."
+  }
+]

changedInput schema / properties / passport_token / description

Previous value: -"Your amp_ token, only if your app has no sign-in and cannot send it as an Authorization header."New value: +"Your amp_ token, only if you have no app sign-in and cannot send a header."

Changed4 schema fields changedOct 13, 2026

removedInput schema / $schema

Removed value: -"https://json-schema.org/draft/2020-12/schema"

changedInput schema / properties / passport_token / description

Previous value: -"Your amp_ token, only if your client cannot send it as an Authorization header; leave it out when your MCP app signed in."New value: +"Your amp_ token, only if your app has no sign-in and cannot send it as an Authorization header."

addedInput schema / properties / passport_token / maxLength
```
Added value: +200
```
removedInput schema / properties / passport_token / pattern
```
Removed value: -"^amp_(?:s_)?[A-Za-z0-9_-]{43}$"
```

Changed8 schema fields changedOct 5, 2026

addedInput schema / additionalProperties
```
Added value: +false
```

addedInput schema / properties / content_type / description

Added value: +"Stored and returned on read. Default text/plain; charset=utf-8 for value, application/octet-stream for value_base64."

addedInput schema / properties / if_match

Added value: +{
+  "description": "Store only if the current value has this etag (from locker_get or locker_put); \"*\": only if the key exists. Otherwise 412 precondition_failed and nothing is stored.",
+  "maxLength": 200,
+  "minLength": 1,
+  "pattern": "^[\\x20-\\x7e]+$",
+  "type": "string"
+}

addedInput schema / properties / if_none_match

Added value: +{
+  "const": "*",
+  "description": "\"*\": store only if the key does not exist yet (create only), else 412 precondition_failed.",
+  "type": "string"
+}

addedInput schema / properties / key / description

Added value: +"Key, 1 to 200 characters from A-Z a-z 0-9 . _ : / - (no spaces; \"/\" separates folders)."

changedInput schema / properties / passport_token / description

Previous value: -"Leave it out when your MCP app signed in to AgentMart (it is refused then). Otherwise your passport bearer token (amp_...) or session token (amp_s_...), only if your client cannot send it as an Authorization header. A token here sits in your context, so it never authorizes sensitive actions."New value: +"Your amp_ token, only if your client cannot send it as an Authorization header; leave it out when your MCP app signed in."

addedInput schema / properties / value / description

Added value: +"The value as text (UTF-8). \"\" stores an empty value."

addedInput schema / properties / value_base64 / description

Added value: +"The value as bytes, in standard base64 with = padding."

First observedOct 4, 2026

TDQS

A4.4/5.0

Behavior4/5

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

Annotations already flag destructiveHint=true and idempotentHint=true; the description adds value beyond that by disclosing persistence across sessions and the optimistic-concurrency behavior (etag returned, if_match guards against clobbering). It stops short of describing what happens to a hidden/unmentioned content_type on overwrite or the exact write-vs-update failure modes, so not a 5.

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?

Three short sentences, front-loaded with purpose, then the value/value_base64 rule, then the concurrency hint. Nothing is padded and each sentence carries distinct information.

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

Completeness4/5

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

For an 8-parameter mutation with no output schema, the description covers the return payload (the etag) and the important write semantics. Secondary parameters like content_type and passport_token are left entirely to the schema, which is acceptable given full schema coverage but leaves room for slightly richer context.

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

Parameters4/5

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

Schema coverage is 100%, so the baseline is 3, but the description adds a cross-parameter constraint the schema does not encode: exactly one of value or value_base64. It also frames the etag workflow for if_match rather than just restating its definition.

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?

States a specific verb and resource (store a value in your memory locker under a key) plus the defining trait that it persists between sessions. It also names locker_get as the etag source, which implicitly separates it from the read/delete/list siblings in the locker_* family.

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

Usage Guidelines4/5

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

Explicitly tells the caller to send exactly one of value or value_base64, and explains the concurrency contract (pass etag as if_match so an overlapping run cannot silently overwrite). It gives clear usage context but never names an alternative tool or states when not to use this instead of, say, share_set or queue_put.

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

All AgentMart tools Inspect

Try in Browser

Shareable, User-Owned Context BackendPeople, applications, and agents read, write, and coordinate together in one context lake. Reach it over MCP, a CLI, a Python SDK, or REST.fulcradynamics.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Store in my memory locker

Input Schema

Schema Changelog

TDQS

Glama MCP Gateway

Resources