MemHeaven

mempalace_get_drawer

Read-onlyIdempotent

Retrieve a tenant-scoped drawer by ID to access its verbatim content and provenance metadata.

Instructions

Fetch one tenant-scoped drawer by id, including bounded verbatim content and provenance metadata.

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": {
      "drawer_id": "<drawer_id>"
    },
    "name": "mempalace_get_drawer"
  }
}

Input Schema

Name	Required	Description	Default
`drawer_id`	Yes	Identifier of the tenant-scoped drawer to retrieve.

Output Schema

Name	Required	Description	Default
`room`	Yes
`wing`	Yes
`content`	Yes
`metadata`	Yes
`drawer_id`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Aug 11, 2026

TDQS

A4.3/5.0

Behavior4/5

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

Annotations already declare read-only, idempotent, and non-destructive behavior. The description adds useful context beyond annotations by stating the response includes bounded verbatim content and provenance metadata, helping the agent set expectations.

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?

The description is a single, information-dense sentence with no filler. It is front-loaded with the action and resource, and every phrase adds value.

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

Completeness5/5

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

For a simple one-parameter retrieval tool with a rich output schema and strong annotations, this description is complete. It conveys the tool's purpose, scope, and what to expect in the response, which is sufficient for selection and invocation.

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?

The schema provides a clear description for drawer_id, and schema coverage is 100%. The description reinforces the parameter's role but does not add new semantic meaning beyond what the schema already offers, so the baseline of 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 uses a specific verb 'Fetch' and a clear resource 'tenant-scoped drawer' with a precise scope qualifier 'by id'. It also adds content details (bounded verbatim content and provenance metadata), which distinguishes it from siblings like mempalace_list_drawers.

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?

The description clearly implies the tool is for retrieving a single drawer when you have its ID. It does not explicitly mention alternatives or when not to use it, but the naming and wording make the intended use case obvious.

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