Skip to main content
Glama
Sign In

Exogram — Personal AI Agent & Workspace

by io.github.Richard-Ewing
OverviewDiscussionsAdmin

search_memory_vault

Search the Exogram Personal Neural Network and encrypted memory vault across facts, people, preferences, and commitments.

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": {
      "query": "<query>"
    },
    "name": "search_memory_vault"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryYesThe search query to match against stored memories, relationships, or project context.
top_kNoNumber of results to return (1-20, default 5).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.9/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full disclosure burden and mostly fails to meet it. 'Search' implies a read, but nothing states whether the vault requires authorization, whether results are ranked or truncated, or what a result record contains; calling the vault 'encrypted' raises security questions the description never resolves.

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?

A single front-loaded sentence with no filler or repetition. It is efficient, though part of its brevity comes from omitting information rather than from tight editing.

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

Completeness2/5

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

For a two-parameter search with no annotations and no output schema, one sentence is thin, especially with four sibling tools that plausibly overlap in retrieval. An agent cannot tell from this definition alone whether to search here, in 'search_vault', or via 'query_graph'.

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?

Schema description coverage is 100%, so the schema already explains 'query' and the 1-20 range on 'top_k'. The description adds only the categories that can be matched (facts, people, preferences, commitments), which is mildly useful context but not parameter-level detail.

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 gives a clear verb ('Search') and names the resource ('Exogram Personal Neural Network and encrypted memory vault') plus the data domains covered (facts, people, preferences, commitments). It is more specific than the tool name alone, but the branded jargon and the absence of any distinction from the sibling 'search_vault' leave the exact scope approximate.

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

Usage Guidelines2/5

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

There is no guidance on when to choose this tool over the closely related 'search_vault', 'query_graph', 'list_entities', or 'get_neural_cluster' siblings. No preconditions, exclusions, or example queries are offered, so the agent must infer routing from the name alone.

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

All Exogram — Personal AI Agent & Workspace toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources