Skip to main content
Glama
Sign In
scoped_memory

scoped_memory

by lixuanfan567-png
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

memory_open_task

Creates a fresh task identity for an initialized project so work starts without inheriting previous task context.

Instructions

Create a fresh task identity for an initialized project; no previous task is inherited.

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": {
      "project_root": "<project_root>"
    },
    "name": "memory_open_task"
  }
}

Input Schema

NameRequiredDescriptionDefault
project_rootYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.4.0

TDQS

B3.3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, idempotentHint=false, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds genuinely new context by stating that no prior task is inherited, i.e. that this starts a clean state. It does not say what happens if the project is not initialized, whether an existing open task is discarded, or what identity is returned.

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 compact sentence with the action front-loaded and the two key constraints (initialized project, fresh identity) following immediately. No filler or redundant restatement of the tool name.

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

Completeness3/5

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

For a non-idempotent state-creating lifecycle tool, the description covers the core semantics but leaves open what state is created, how failure on an uninitialized project is reported, and what the caller receives (no output schema exists to compensate). Adequate as a minimum-viable definition, but incomplete for a stateful tool.

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?

There is one parameter (project_root) with 0% schema description coverage, so the description carries the full burden and does not meet it. "An initialized project" weakly implies project_root is the project directory, but no path format, resolution behavior, or expected value is given.

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?

States a specific verb and resource ("Create a fresh task identity") plus a scope condition ("for an initialized project") and an explicit negation ("no previous task is inherited"), which separates it from lifecycle siblings like memory_close_task and memory_init_project. It stops short of naming a sibling outright, so the differentiation is implied rather than explicit.

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

Usage Guidelines3/5

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

The phrase "for an initialized project" encodes a prerequisite, implying memory_init_project must run first, and "no previous task is inherited" hints at a fresh-session scenario. There is no explicit when-to-use/when-not-to-use statement and no routing to alternatives such as memory_task_context or memory_close_task.

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