Skip to main content
Glama

kb_get_preferences

Retrieve stored user preferences to personalize interactions and maintain context across AI sessions.

Instructions

Get user preferences

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • src/index.ts:223-230 (registration)
    Registration of the kb_get_preferences tool in the tools array, defining name, description, and empty input schema.
    {
      name: 'kb_get_preferences',
      description: 'Get user preferences',
      inputSchema: {
        type: 'object',
        properties: {}
      }
    },
  • MCP tool handler that executes kb_get_preferences by retrieving preferences via KnowledgeManager and returning as JSON-formatted text content.
    case 'kb_get_preferences': {
      return {
        content: [
          {
            type: 'text',
            text: JSON.stringify(km.getPreferences(), null, 2)
          }
        ]
      };
    }
  • Core helper method returning a shallow copy of preferences from the internal knowledge base storage.
    getPreferences(): Preferences {
      return { ...this.kb.preferences };
    }
Behavior2/5

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

No annotations are provided, so the description carries full burden. It states a read operation ('Get'), implying it's likely safe, but doesn't disclose behavioral traits like authentication needs, rate limits, or what 'preferences' encompasses (e.g., defaults vs. custom settings).

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?

The description is a single, efficient sentence with zero waste. It's front-loaded and appropriately sized for a simple tool, though it could benefit from more detail given the lack of annotations.

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?

Given no annotations, no output schema, and multiple sibling tools, the description is incomplete. It doesn't clarify what 'preferences' includes or how it differs from other 'kb_get_*' tools, leaving gaps for an agent to understand context and usage.

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?

With 0 parameters and 100% schema coverage, the baseline is high. The description adds no parameter details, but since there are no parameters to document, this is acceptable. It implies no inputs are needed, which aligns with the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description 'Get user preferences' clearly states the action (Get) and resource (user preferences), but it's vague about scope or format. It doesn't differentiate from sibling tools like 'kb_get_personal' or 'kb_get_professional', which likely retrieve specific preference subsets.

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?

No guidance is provided on when to use this tool versus alternatives. With siblings like 'kb_get_personal' and 'kb_get_professional', the description doesn't indicate if this retrieves all preferences or a specific category, leaving usage unclear.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/hlsitechio/mcp-instruct'

If you have feedback or need assistance with the MCP directory API, please join our Discord server