Skip to main content
Glama
Sign In

Kosmodrom

by ai.kosmodrom
OverviewDiscussionsAdmin

memory_create

Saves a confirmed fact, rule or recipe as an agent memory record when the user asks to keep knowledge for future agent work; secrets only at the user's direct request. The record starts personal and unverified: it applies to the token owner's agents at once, and a moderator can make it shared. level is the scope: company (Git, cloud, CI), user (personal preferences), project (stands, addresses, project infrastructure) or repository (conventions, tests, code pitfalls).

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": {
      "level": "<level>",
      "load": "<load>",
      "title": "<title>",
      "text": "<text>"
    },
    "name": "memory_create"
  }
}

Input Schema

NameRequiredDescriptionDefault
jobsNoJobs the record is for; at least one for job and request, none for always.
loadYesalways - delivered with any work, short; job - with the jobs in `jobs` (prevention, silent pitfalls); request - only in the `memory` index, read by ID (symptom diagnostics, narrow areas).
textYesOne topic, 1.5-3 thousand characters (max 4,000), in the language of the workspace data: rules and facts with reasons. Author and date are record fields, no "Source" line needed.
levelYes
titleYes"<area> · <situation or symptom>: <what's inside>", up to 200 characters, in the language of the workspace data; agents judge relevance by the title in the memory index.
agentsNoWhich agents the record is for: all - everyone (default); user - agents working on a person's token, with that person's machine setup; system - Kosmodrom agent employees working on their own VM under the agent runner.
projectIDNoProject ID, for level = project.
productIDsNoFor level = project: the products where the record is delivered. Products of its own project: only in them (none of them listed - in all products of the project); products of other projects: in them too.
repositoryIDNoRepository ID, for level = repository.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / jobs / items / enum
      Previous value: -[
-  "analysis",
-  "dev",
-  "qa",
-  "devops",
-  "review",
-  "design"
-]New value: +[
+  "analysis",
+  "dev",
+  "qa",
+  "devops",
+  "review",
+  "design",
+  "marketing"
+]
    • changedInput schema / properties / jobs / maxItems
      Previous value: -6New value: +7
  2. Changed1 schema field changed
    • addedInput schema / properties / agents
      Added value: +{
+  "description": "Which agents the record is for: all - everyone (default); user - agents working on a person's token, with that person's machine setup; system - Kosmodrom agent employees working on their own VM under the agent runner.",
+  "enum": [
+    "user",
+    "all",
+    "system"
+  ],
+  "type": "string"
+}
  3. Changed2 schema fields changed
    • addedInput schema / properties / productIDs
      Added value: +{
+  "description": "For level = project: the products where the record is delivered. Products of its own project: only in them (none of them listed - in all products of the project); products of other projects: in them too.",
+  "items": {
+    "format": "uuid",
+    "type": "string"
+  },
+  "maxItems": 50,
+  "type": "array"
+}
    • changedInput schema / properties / title / description
      Previous value: -"\"<area> · <situation or symptom>: <what's inside>\", up to 200 characters, in the language of the workspace data; agents judge relevance by it, and agents doing other kinds of work see it only up to \": \"."New value: +"\"<area> · <situation or symptom>: <what's inside>\", up to 200 characters, in the language of the workspace data; agents judge relevance by the title in the memory index."
  4. Changed2 schema fields changed
    • removedInput schema / $schema
      Removed value: -"http://json-schema.org/draft-07/schema#"
    • changedInput schema / properties / title / description
      Previous value: -"\"<area> · <situation or symptom>: <what's inside>\", up to 200 characters, in the language of the workspace data; agents judge relevance by it."New value: +"\"<area> · <situation or symptom>: <what's inside>\", up to 200 characters, in the language of the workspace data; agents judge relevance by it, and agents doing other kinds of work see it only up to \": \"."
  5. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already flag this as a non-read-only, non-destructive, closed-world write. The description adds genuinely new behavior: the record starts personal and unverified, applies immediately to the token owner's agents, and a moderator can later make it shared — lifecycle and visibility facts the agent cannot infer from annotations. It doesn't mention limits or failure modes, keeping it at 4.

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

Conciseness4/5

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

The purpose and trigger are front-loaded in the first clause, with the record lifecycle and scope guidance following. It is dense but every sentence carries content; the level enumeration sentence is long but necessary.

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 a 9-parameter mutation with no output schema, the description supplies what the schema can't: when to create, secrecy policy, and default visibility/lifecycle. Remaining gaps (what an ID-returning response looks like, behavior on validation failure) are minor given no output schema and high schema coverage.

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 89%, so the baseline is 3, but the description adds a real gloss on `level` (what company, user, project and repository mean) that the schema leaves as a bare enum. That's a meaningful semantic addition beyond structured fields.

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 opens with a specific verb and resource ('Saves a confirmed fact, rule or recipe as an agent memory record') and scopes it to the trigger ('when the user asks to keep knowledge for future agent work'). That distinguishes it cleanly from memory_list, memory_read and memory_update without needing their schemas.

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?

It states the trigger condition (user wants knowledge kept for future agent work) and a real exclusion ('secrets only at the user's direct request'). It explains how the `level` scope decisions map to situations (company/user/project/repository). It stops short of naming memory_update as the alternative for revising an existing record, so it's slightly below a full 5.

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

All Kosmodrom toolsInspect
Try in Browser
Claude Code, inside the Godot 4 editorFlockbay puts an AI agent in the real Godot 4 editor: it writes GDScript, runs your game and fixes what breaks. Free, or bring your own Claude Code or Codex.flockbay.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources