Skip to main content
Glama

get_worldview

Retrieve current worldview primitives and beliefs to understand system perspectives and maintain continuity in AI memory storage.

Instructions

Retrieve current worldview primitives and beliefs

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The actual implementation of getWorldviewPrimitives() method that queries the worldview_primitives table, ordered by confidence and stability score
    async getWorldviewPrimitives() {
      try {
        const primitives = await this.db
          .select()
          .from(schema.worldviewPrimitives)
          .orderBy(
            desc(schema.worldviewPrimitives.confidence),
            desc(schema.worldviewPrimitives.stabilityScore)
          );
    
        return primitives;
      } catch (error) {
        console.error('Error getting worldview primitives:', error);
        throw error;
      }
    }
  • Tool schema definition for get_worldview with description and empty input parameters
    name: "get_worldview",
    description: "Retrieve current worldview primitives and beliefs",
    inputSchema: {
      type: "object",
      properties: {}
    }
  • mcp.js:589-591 (registration)
    MCP server request handler that routes get_worldview calls to the memory manager method
    case "get_worldview":
      const worldview = await memoryManager.getWorldviewPrimitives();
      return { content: [{ type: "text", text: JSON.stringify(worldview, null, 2) }] };
  • mcp.js:191-196 (registration)
    MCP server tool registration for get_worldview in ListToolsRequestSchema handler
    name: "get_worldview",
    description: "Retrieve current worldview primitives and beliefs",
    inputSchema: {
      type: "object",
      properties: {}
    }
  • Database schema definition for worldview_primitives table with category, belief, confidence, emotionalValence, and other fields
    export const worldviewPrimitives = pgTable("worldview_primitives", {
    	id: uuid().defaultRandom().primaryKey().notNull(),
    	category: text().notNull(),
    	belief: text().notNull(),
    	confidence: doublePrecision(),
    	emotionalValence: doublePrecision("emotional_valence"),
    	stabilityScore: doublePrecision("stability_score"),
    	connectedBeliefs: uuid("connected_beliefs").array(),
    	activationPatterns: jsonb("activation_patterns"),
    	memoryFilterRules: jsonb("memory_filter_rules"),
    	influencePatterns: jsonb("influence_patterns"),
    	preferredClusters: uuid("preferred_clusters").array(),
    });
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. While 'Retrieve' implies a read-only operation, it doesn't specify whether this requires permissions, how current the data is, potential rate limits, or what format the output takes. For a tool with zero annotation coverage, this leaves significant behavioral gaps.

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 that gets straight to the point with no wasted words. It's appropriately sized for a zero-parameter tool and front-loads the essential information about what the tool does.

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?

Given the tool has no parameters, no output schema, and no annotations, the description provides the minimum viable information about what the tool retrieves. However, for a tool that presumably returns important system state information, more context about what 'worldview primitives and beliefs' encompass and how this differs from related sibling tools would be beneficial.

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 description coverage, the baseline is 4. The description appropriately doesn't waste space discussing non-existent parameters, though it could potentially clarify that no filtering or configuration options are available for this retrieval operation.

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 clearly states the action ('Retrieve') and the target ('current worldview primitives and beliefs'), providing a specific verb+resource combination. However, it doesn't explicitly differentiate from sibling tools like 'get_identity_core' or 'get_active_themes', which might retrieve related but different aspects of the system's state.

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?

The description provides no guidance on when to use this tool versus alternatives. With sibling tools like 'get_identity_core' and 'get_active_themes' that might retrieve overlapping or related information, there's no indication of when this specific tool is appropriate or what distinguishes it from those options.

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/randyandrade/agi-mcp-server'

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