Skip to main content
Glama

DeNasty Memory

My preferences

my_preferences
Read-only

Returns the user's confirmed personal preferences and writing rules that they allowed to share with AI tools.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnlyHint=true, openWorldHint=false), so the bar is lower. The description still adds non-obvious context by disclosing the data scope: only confirmed preferences and only those the user consented to share, which tells the agent results may be partial and requires no auth action. It omits what an empty result looks like, but that is a minor gap given the annotations.

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?

One sentence, front-loaded with the verb and resource, with every qualifier ('confirmed', 'allowed to share') carrying real meaning about what comes back. No filler or restatement of the title.

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 input parameters and no output schema, the description must carry more of the return-value burden, and it only characterizes the content as 'personal preferences and writing rules'. It does not indicate shape, grouping, or empty-state behavior, which an agent would need to parse results reliably.

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 there is no parameter semantics to explain and the baseline is 4. The description correctly implies the call needs no arguments or identifiers, matching the empty schema.

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?

"Returns the user's confirmed personal preferences and writing rules" gives a specific verb plus a well-scoped resource, with two meaningful qualifiers: 'confirmed' and 'allowed to share with AI tools'. It does not name any sibling (recall, remember, project_brief) to differentiate itself, which keeps it at 4 rather than 5.

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?

Usage is only implied: an agent can infer it should call this to fetch user preferences before personalizing output, and should not expect unconfirmed or non-shared data. There is no explicit when-to-use statement, no mention of how it relates to recall/remember, and no guidance on whether it must be called at session start.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources