Skip to main content
Glama
Sign In
ZeroDB Agent Memory MCP Server

ZeroDB Agent Memory MCP Server

by AINative-Studio
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Hybrid

zerodb_plan_get

Retrieve a plan by ID to restore a previous session's plan when starting a new session.

Instructions

Retrieve a plan artifact by ID. Use this at session start to restore a plan from a previous session.

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": {
      "id": "<id>"
    },
    "name": "zerodb_plan_get"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesArtifact ID returned by zerodb_plan_create

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.2.7

TDQS

A4.1/5.0
Behavior3/5

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

No annotations are provided, so the description carries the burden. It uses 'Retrieve' to imply a read-only operation, and 'restore' suggests state recovery. However, it does not disclose outcomes for missing IDs, errors, or any side effects, leaving some ambiguity for a tool with no annotation support.

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 two sentences: the first states the primary function, and the second adds usage context. It is front-loaded, efficient, and contains no redundant information.

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 retrieval tool with one well-documented parameter and no output schema, the description covers the core purpose and typical usage scenario. It is sufficiently complete for an agent to understand when and how to use it.

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 input schema provides full coverage of the 'id' parameter with a clear description ('Artifact ID returned by zerodb_plan_create'). The tool description adds little beyond that, so baseline 3 is appropriate given 100% schema coverage.

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 clearly states the action ('Retrieve a plan artifact by ID') and identifies the specific resource (a plan artifact). This distinguishes it from siblings like zerodb_plan_create, zerodb_plan_update, and zerodb_plan_history, which handle different operations.

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 provides a clear when-to-use scenario: 'Use this at session start to restore a plan from a previous session.' This gives practical context, though it does not explicitly mention alternatives or when not to use the tool.

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

Deploy Server

Other Tools