Quorus

Official

by Quorus-dev

Overview Schema Source Related Servers Discussions Admin

Python

Local

memory_set

Store a value under a key in an agent's per-room persistent memory so it can be retrieved later.

Instructions

Store a value in this agent's per-room persistent memory.

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_id": "<room_id>",
      "key": "<key>",
      "value": "<value>"
    },
    "name": "memory_set"
  }
}

Input Schema

Name	Required	Default
`key`	Yes
`value`	Yes
`room_id`	Yes
`visibility`	No	private

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.5.2Oct 18, 2026

TDQS

C2.8/5.0

Behavior2/5

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

No annotations exist, so the description carries the full behavioral burden. It usefully adds that memory is persistent, agent-owned, and per-room, but is silent on the critical set semantics: whether an existing key is overwritten, what 'visibility' controls, size limits, or permission/auth requirements for a mutation.

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?

A single front-loaded sentence with no filler; the core action and scope lead the sentence. Nothing is repeated or wasted.

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?

An output schema exists, so return values need not be explained, but for a 4-parameter mutation with zero schema descriptions and no annotations the definition is under-specified. Overwrite behavior, visibility values, and authorization are all missing.

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

Parameters2/5

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

Schema coverage is 0% across 4 parameters and the description mentions none of them by name. 'Store a value' and 'per-room' weakly imply the value and room_id params, but key semantics and the visibility parameter (default 'private', no enum, no description) are entirely opaque.

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?

Specific verb + resource: 'Store a value in this agent's per-room persistent memory' clearly identifies a write-to-memory operation. It is distinguishable from siblings like memory_get/memory_delete, though it never names them explicitly.

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 on when to use this versus memory_get, memory_list, memory_delete, or the room-state tools. No prerequisites, no mention that room_id scopes the write, and no exclusions. The 'per-room' phrase implies scope but nothing about selection.

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