Skip to main content
Glama

kb_update_projects

Update project context including current projects, technologies used, goals, challenges, team size, and methodology for AI memory storage.

Instructions

Update project context (current projects, technologies, goals)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
currentProjectsNo
technologiesNo
goalsNo
challengesNo
teamSizeNo
methodologyNo

Implementation Reference

  • MCP tool handler case that calls KnowledgeManager.updateProjects with input arguments and returns success response.
    case 'kb_update_projects': {
      await km.updateProjects(args as any);
      return {
        content: [
          {
            type: 'text',
            text: '✅ Project context updated successfully'
          }
        ]
      };
    }
  • Core implementation that merges partial ProjectContext updates into the knowledge base projects section, logs history, and persists to file.
    async updateProjects(updates: Partial<ProjectContext>): Promise<void> {
      Object.entries(updates).forEach(([field, value]) => {
        const oldValue = (this.kb.projects as any)[field];
        (this.kb.projects as any)[field] = value;
        this.addHistory({
          action: oldValue === undefined ? 'add' : 'update',
          category: 'projects',
          field,
          oldValue,
          newValue: value
        });
      });
      await this.save();
    }
  • Input schema definition and tool registration in the tools list returned by ListToolsRequestHandler.
    {
      name: 'kb_update_projects',
      description: 'Update project context (current projects, technologies, goals)',
      inputSchema: {
        type: 'object',
        properties: {
          currentProjects: { type: 'array', items: { type: 'string' } },
          technologies: { type: 'array', items: { type: 'string' } },
          goals: { type: 'array', items: { type: 'string' } },
          challenges: { type: 'array', items: { type: 'string' } },
          teamSize: { type: 'number' },
          methodology: { type: 'string' }
        }
      }
    },
Behavior2/5

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

With no annotations provided, the description carries full burden but only states it's an update operation. It doesn't disclose behavioral traits such as permissions needed, whether it overwrites or merges data, error conditions, or what happens if parameters are omitted. This is inadequate 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 that front-loads the core purpose. Every word earns its place with no redundancy or 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?

For a mutation tool with 6 parameters, 0% schema coverage, no annotations, and no output schema, the description is incomplete. It should explain more about the update behavior, parameter interactions, and expected outcomes to compensate for the lack of structured data.

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?

The description lists three parameters (currentProjects, technologies, goals) but the schema has six parameters total with 0% coverage. It adds some meaning by naming these fields, but doesn't explain the other three parameters (challenges, teamSize, methodology) or provide format details, leaving significant gaps.

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 ('Update') and resource ('project context'), specifying the fields being updated (current projects, technologies, goals). It distinguishes from some siblings like kb_get_projects (read vs. write) but doesn't explicitly differentiate from other update tools like kb_update_personal or kb_update_professional.

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. It doesn't mention prerequisites, timing, or compare with sibling tools like kb_update_personal or kb_get_projects, leaving the agent to infer usage context.

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