Skip to main content
Glama

get_user_preferences

Retrieve saved global developer preferences and coding rules, optionally filtered by category, to keep AI coding agents consistent across sessions and tools.

Instructions

Retrieve all saved global developer preferences and coding rules.

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

Input Schema

NameRequiredDescriptionDefault
categoryNoOptional category filter.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.3.0

TDQS

B3.1/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. "Retrieve" and "all" imply a read-only, complete-list operation with no pagination, which is useful, but nothing is said about permissions, return shape, or empty results.

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, and free of filler. Every word contributes to scope or subject matter.

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?

For a single-param read tool with no output schema, the description is minimally sufficient: the agent knows what it fetches and that it is a full read. It lacks the return-value shape and permission expectations that would make it complete for an unannotated tool.

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% and the single optional category parameter is already documented as an "Optional category filter." The description adds no parameter meaning beyond that, so the baseline 3 applies; the word "all" slightly undersells that filtering is possible.

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?

"Retrieve all saved global developer preferences and coding rules" names a specific verb (retrieve) and a concrete resource (preferences and coding rules), with scope qualifiers "all" and "global". That distinguishes it from the write-side sibling set_user_preference by implication, though the description never names that counterpart.

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 explicit when-to-use or when-not-to-use guidance, and no alternative tool is named. The word "all" hints at the unfiltered read case, but an agent must still infer that set_user_preference is the write counterpart and that this tool should be used for reading rather than writing preferences.

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