Skip to main content
Glama

dejo_memory

Read-only

Reads stored website memory to list explored trails, inspect a trail's steps, map seen pages and controls, or view routes shared by other agents.

Instructions

What Dejo remembers about websites. Read only. what=sites lists every trail and its health; what=show gives one trail's steps; what=map lists pages seen on a site (with path: that page's controls); what=commons lists trails other agents shared.

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": {
      "what": "<what>"
    },
    "name": "dejo_memory"
  }
}

Input Schema

NameRequiredDescriptionDefault
pathNo
siteNo
taskNo
whatYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.5.0

TDQS

B3.4/5.0
Behavior3/5

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

"Read only" merely restates readOnlyHint=true, so it earns no credit beyond annotations. The description does add genuine behavioral detail in "what=map ... (with path: that page's controls)", revealing that path drills into page controls, but says nothing about staleness of memory, missing-data behavior, or result shape for a tool whose whole value is recall fidelity.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded with the identity sentence, then a compact semicolon-delimited mode table — dense and scannable with essentially no filler. The only waste is "Read only," which duplicates the annotation.

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?

With no output schema the description must at least orient the agent to return content, which the per-mode clauses do adequately. But for a four-parameter, four-mode tool it leaves the parameter-to-mode binding unstated, which is the one thing an agent most needs before invoking it.

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 description coverage is 0%, so the description carries the full burden, and it only partly discharges it: the four `what` values are given real meaning and `path` is glossed. `site` and `task` are never mentioned, leaving the agent to guess that site pairs with map and task with show — the exact mapping needed to call the tool correctly.

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?

The description names a concrete resource ("what Dejo remembers about websites") and decomposes it into four distinct modes (sites, show, map, commons), so an agent can tell it apart from dejo_login/dejo_manage/dejo_run, which are action tools. The verb is somewhat implicit ("remembers"), but the mode enumeration makes the scope unambiguous.

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?

Each enum value gets a one-clause explanation of what it returns (health per trail, one trail's steps, pages on a site, shared trails), which functions as clear per-mode usage guidance. What's missing is any explicit routing versus siblings or note about which companion parameters each mode expects.

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