Skip to main content
Glama

kb_update_professional

Update professional details like job, skills, experience, and education to maintain current career information in your knowledge base.

Instructions

Update professional information (job, skills, experience, etc.)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
occupationNo
yearsOfExperienceNo
industryNo
specializationsNo
currentCompanyNo
roleNo
skillsNo
certificationsNo
educationNo

Implementation Reference

  • MCP tool dispatch handler for 'kb_update_professional'. Delegates to KnowledgeManager.updateProfessional and returns success response.
    case 'kb_update_professional': {
      await km.updateProfessional(args as any);
      return {
        content: [
          {
            type: 'text',
            text: '✅ Professional information updated successfully'
          }
        ]
      };
    }
  • Core implementation that updates professional info in knowledge base, records history change, and persists to disk.
    async updateProfessional(updates: Partial<ProfessionalInfo>): Promise<void> {
      Object.entries(updates).forEach(([field, value]) => {
        const oldValue = (this.kb.professional as any)[field];
        (this.kb.professional as any)[field] = value;
        this.addHistory({
          action: oldValue === undefined ? 'add' : 'update',
          category: 'professional',
          field,
          oldValue,
          newValue: value
        });
      });
      await this.save();
    }
  • Tool registration and input schema definition for kb_update_professional, defining expected parameters.
    {
      name: 'kb_update_professional',
      description: 'Update professional information (job, skills, experience, etc.)',
      inputSchema: {
        type: 'object',
        properties: {
          occupation: { type: 'string' },
          yearsOfExperience: { type: 'number' },
          industry: { type: 'string' },
          specializations: { type: 'array', items: { type: 'string' } },
          currentCompany: { type: 'string' },
          role: { type: 'string' },
          skills: { type: 'array', items: { type: 'string' } },
          certifications: { type: 'array', items: { type: 'string' } },
          education: { type: 'array', items: { type: 'string' } }
        }
      }
    },
  • TypeScript interface defining the structure of professional information, matching the tool input schema.
    export interface ProfessionalInfo {
      occupation?: string;
      yearsOfExperience?: number;
      industry?: string;
      specializations?: string[];
      currentCompany?: string;
      role?: string;
      skills?: string[];
      certifications?: string[];
      education?: string[];
    }
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. 'Update' implies a mutation operation, but the description doesn't specify whether this requires authentication, what happens to existing data, if changes are reversible, or any rate limits. It lacks critical behavioral details needed for safe and effective use.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/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 without unnecessary words. It's appropriately sized for a tool with many parameters, though it could be more structured by front-loading key details about the update operation.

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 (9 parameters, mutation operation) and lack of annotations or output schema, the description is incomplete. It doesn't address behavioral risks, parameter details, or expected outcomes, leaving significant gaps for the agent to navigate without sufficient context.

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?

The input schema has 9 parameters with 0% description coverage, meaning all parameters are undocumented in the schema. The description only vaguely references 'professional information (job, skills, experience, etc.)', which maps to some parameters but doesn't explain their semantics, formats, or relationships. It fails to compensate for the poor schema coverage.

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 resource ('professional information') with specific examples (job, skills, experience, etc.), making the purpose immediately understandable. However, it doesn't distinguish this tool from sibling tools like 'kb_update_personal' or 'kb_update_projects' beyond the 'professional' qualifier, which is why it doesn't reach a perfect score.

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. It doesn't mention prerequisites, context, or relationships with sibling tools like 'kb_get_professional' (for retrieval) or other update tools, leaving the agent to infer usage based solely on the tool name.

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