Skip to main content
Glama

X1 Wealth

by com.x1wealth
OverviewDiscussionsAdmin

Client Decision Memory

get_client_memory
Read-onlyIdempotent

Recall recorded X1 decision memory for your own record or an assigned client, with category filtering, timestamps, status, owner labels, confidence, and provenance. Set drafts to authored_by_me to read back only pending drafts written by the connected user; every other professional draft remains private. Scoped specialists are excluded.

Input Schema

NameRequiredDescriptionDefault
limitNoMaximum number of memory entries to return, capped at 50.
draftsNoSet to authored_by_me to include only pending decision drafts written by the connected user. Drafts from every other author remain private.
categoryNoOptional decision-memory category filter.
clientIdNoAssigned client or member user ID. Members may omit it for their own record; professionals must pass it unless X1 already supplied a client-scoped context.
questionNoQuestion used to retrieve relevant recorded work before the response limit.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / question
      Added value: +{
+  "description": "Question used to retrieve relevant recorded work before the response limit.",
+  "maxLength": 1000,
+  "minLength": 1,
+  "type": "string"
+}
  2. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, and non-destructive behavior, so the safety profile is covered. The description adds genuine behavioral context beyond that: the privacy rule that non-authored drafts remain private, and the access restriction excluding scoped specialists. It does not describe pagination or return ordering, so not a 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 the core purpose, then constraints, in three sentences with little filler. The drafts sentence overlaps heavily with the schema's drafts description, which is the only notable redundancy.

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

Completeness4/5

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

For a five-parameter read tool with no output schema, the description covers purpose, access scope, privacy behavior, and hints at returned fields. It stops short of explaining result ordering or how question-based retrieval works, a minor gap given the rich schema.

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 coverage is 100%, so all five parameters are already well documented. The description largely restates the drafts parameter rather than adding new semantics (e.g., how 'category' values are matched or how 'question' ranks results), so the baseline 3 is appropriate.

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 ('Recall') and resource ('recorded X1 decision memory') with scope ('your own record or an assigned client') and enumerates the fields returned (category, timestamps, status, owner labels, confidence, provenance). This is readily distinguishable from siblings like get_client_profile or get_client_activity without opening their schemas.

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?

Gives clear context for use: recall memory for one's own record or an assigned client, with an explicit exclusion ('Scoped specialists are excluded') and a conditional ('professionals must pass clientId unless X1 supplied context'). It does not name an alternative tool for overlapping reads, which keeps it short of a 5.

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

All X1 Wealth toolsInspect
Try in Browser
Context All Your Agents Can ShareAgents share what they learn, hand off work, and hold it when you switch models. Start with 5 GB free.fulcradynamics.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources