Skip to main content
Glama
Sign In
ai-dememory

ai-dememory

by GonzaloTorreras
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Memory Schedule Environment

memory.schedule_environment
Read-only

Assess local scheduler, Docker, and crontab command availability on Windows, Linux, or macOS in installed or Docker mode. Determine environment readiness without running commands.

Instructions

Check local scheduler, Docker, and crontab command availability without running commands.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "memory.schedule_environment"
  }
}

Input Schema

NameRequiredDescriptionDefault
modeNoinstalled
platformNo

Output Schema

NameRequiredDescriptionDefault
modeYes
readyYes
checksYes
platformYes
runs_commandsYes
mutates_systemYes
required_missingYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.0.0

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already indicate readOnlyHint=true and destructiveHint=false. The description adds that it performs checks 'without running commands', but this does not provide additional behavioral context beyond the annotation safety profile.

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 sentence front-loaded with the verb and resource, containing no filler or redundancy. It is optimally concise.

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?

While the tool has only two parameters and is a simple check, the description does not explain return values or output structure. The agent must infer from the name and purpose. With an output schema potentially available but not shown, completeness is adequate but not thorough.

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

Parameters1/5

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

Schema description coverage is 0%, and the description does not mention any parameters. Despite only two enum parameters, the agent receives no guidance on what 'mode' or 'platform' control, leaving the schema to bear all meaning.

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?

Description clearly states 'Check local scheduler, Docker, and crontab command availability' with a specific verb and resources, distinguishing it from sibling tools like memory.schedule_plan and memory.schedule_status which involve planning or status checks.

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 description implies a safe, non-destructive check but does not explicitly state when to use this tool versus alternatives like schedule_plan or schedule_status. No guidance on prerequisites or exclusions.

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