Skip to main content
Glama
phygital-memory

phygital-memory

Official

status

Read-only

Lists the person's memory folders with lock state, note counts, subfolders, privacy, and read/edit permissions. Call it first to choose valid folders for other tools.

Instructions

Start here. Lists the person's memories (folders) you may use: each one's name, whether it is unlocked, how many notes it holds, its main subfolders with a line about each, and which subfolders are private. Also says whether this AI app may only read or may edit. Read only, no inputs. Call it first in a chat, and again when another tool says a folder is locked or unknown. Use the names it gives as folder= in the other tools, and a subfolder as inside= in search_notes when a question clearly belongs there. To see what is inside a folder, use list_notes.

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": "status"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.6/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, and the description's 'Read only, no inputs' merely restates that (no credit). What it adds beyond annotations is the permission context ('whether this AI app may only read or may edit') and the error-recovery loop of re-calling when a folder is locked or unknown — genuinely useful behavioral context. It stops short of describing output shape or cost, hence 4 rather than 5.

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 'Start here' and packed with actionable content, with essentially no filler sentences. The opening sentence is long and enumerates return fields in a run-on way, but every clause carries information an agent needs to interpret the response.

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?

An output schema exists, so the description need not explain return values, yet it summarizes them enough to prime the agent. It covers invocation order, the locked/unknown retry condition, and how outputs feed sibling tools — everything needed to call it correctly and use the result.

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

Parameters4/5

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

The tool takes zero parameters, so the schema has nothing to document and the baseline is 4. The description goes further by explaining how the returned folder and subfolder names become the folder= and inside= arguments of sibling tools, which is parameter guidance in a useful indirect form.

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?

States a specific verb and resource ('Lists the person's memories (folders)') and enumerates exactly what each entry contains: name, lock state, note count, main subfolders, and private subfolders. It also explicitly distinguishes itself from list_notes ('To see what is inside a folder, use list_notes'), so an agent can separate it from the closest sibling without opening either schema.

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

Usage Guidelines5/5

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

Gives explicit invocation timing ('Call it first in a chat, and again when another tool says a folder is locked or unknown') plus re-entry conditions that are not obvious. It also explains downstream wiring: use returned names as folder= in other tools and as inside= in search_notes, and names list_notes as the alternative for depth. Nothing is left to inference.

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