Skip to main content
Glama

kb_update_personal

Update personal details like name, location, languages, and preferences to maintain accurate user context for AI interactions.

Instructions

Update personal information (name, location, languages, etc.)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameNo
birthYearNo
birthPlaceNo
currentLocationNo
languagesNo
nationalityNo
timezoneNo
pronounsNo

Implementation Reference

  • MCP tool handler for kb_update_personal: delegates to KnowledgeManager.updatePersonal and returns success message
    case 'kb_update_personal': {
      await km.updatePersonal(args as any);
      return {
        content: [
          {
            type: 'text',
            text: '✅ Personal information updated successfully'
          }
        ]
      };
    }
  • Core implementation of personal information update: merges partial updates into knowledge base, adds history entry, persists to JSON file
    async updatePersonal(updates: Partial<PersonalInfo>): Promise<void> {
      Object.entries(updates).forEach(([field, value]) => {
        const oldValue = (this.kb.personal as any)[field];
        (this.kb.personal as any)[field] = value;
        this.addHistory({
          action: oldValue === undefined ? 'add' : 'update',
          category: 'personal',
          field,
          oldValue,
          newValue: value
        });
      });
      await this.save();
    }
  • Input schema definition for kb_update_personal tool, defining expected parameters for personal info updates
      name: 'kb_update_personal',
      description: 'Update personal information (name, location, languages, etc.)',
      inputSchema: {
        type: 'object',
        properties: {
          name: { type: 'string' },
          birthYear: { type: 'number' },
          birthPlace: { type: 'string' },
          currentLocation: { type: 'string' },
          languages: { type: 'array', items: { type: 'string' } },
          nationality: { type: 'string' },
          timezone: { type: 'string' },
          pronouns: { type: 'string' }
        }
      }
    },
  • src/index.ts:423-425 (registration)
    Registers all tools including kb_update_personal by returning the tools array in ListToolsRequestSchema handler
    server.setRequestHandler(ListToolsRequestSchema, async () => {
      return { tools };
    });
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 'update' which implies mutation, but doesn't disclose behavioral traits like permissions needed, whether changes are reversible, side effects, or response format. This is a significant gap for a mutation tool with zero annotation coverage.

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 appropriately sized and front-loaded, clearly stating the tool's purpose without unnecessary elaboration.

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 the complexity (8 parameters, mutation operation), lack of annotations, and no output schema, the description is incomplete. It doesn't cover behavioral aspects, full parameter details, or return values, making it inadequate for safe and effective use by an AI agent.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description must compensate. It lists examples (name, location, languages, etc.) that map to some parameters, but doesn't explain semantics for all 8 parameters (e.g., birthYear format, languages array structure, timezone format). It adds marginal value but doesn't fully address the coverage gap.

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 verb 'update' and the resource 'personal information', with examples of specific fields (name, location, languages). It distinguishes from siblings like kb_update_preferences or kb_update_professional by focusing on personal data, though it doesn't explicitly name alternatives.

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 on when to use this tool versus alternatives is provided. It doesn't mention prerequisites, such as whether personal information must already exist, or contrast with siblings like kb_get_personal for retrieval. Usage is implied but not explicitly defined.

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