Skip to main content
Glama

kb_get_projects

Retrieve project context from personal knowledge storage to provide AI agents with structured information about ongoing work and organizational data.

Instructions

Get project context

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • Tool schema definition for 'kb_get_projects', including name, description, and empty input schema.
    {
      name: 'kb_get_projects',
      description: 'Get project context',
      inputSchema: {
        type: 'object',
        properties: {}
      }
    },
  • Main handler for executing 'kb_get_projects' tool. Calls KnowledgeManager.getProjects() and returns JSON string.
    case 'kb_get_projects': {
      return {
        content: [
          {
            type: 'text',
            text: JSON.stringify(km.getProjects(), null, 2)
          }
        ]
      };
    }
  • Helper method in KnowledgeManager that retrieves and returns the projects section of the knowledge base.
    getProjects(): ProjectContext {
      return { ...this.kb.projects };
    }
Behavior1/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. 'Get project context' implies a read operation but reveals nothing about what 'context' entails, whether it requires authentication, has rate limits, returns structured data, or involves any side effects. For a tool with zero annotation coverage, this description fails to provide essential behavioral context.

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

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

While concise with only three words, the description is under-specified rather than efficiently structured. It lacks front-loaded clarity and fails to earn its place by providing meaningful information beyond the tool name. True conciseness balances brevity with usefulness, which is not achieved here.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness1/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the complexity implied by 'project context' and the lack of annotations and output schema, the description is completely inadequate. It does not explain what 'context' means, what format it returns, or how it relates to other knowledge base tools. For a tool that likely retrieves structured project data, this leaves critical gaps in understanding its function and output.

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?

The tool has 0 parameters with 100% schema description coverage, so the schema fully documents the absence of inputs. The description does not add parameter information, which is appropriate here. Baseline is 4 for zero-parameter tools, as there is no need to compensate for schema gaps.

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

Purpose2/5

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

The description 'Get project context' is a tautology that essentially restates the tool name 'kb_get_projects' without adding meaningful specificity. It uses a generic verb 'Get' and vague resource 'project context' without distinguishing what type of context or how it differs from sibling tools like 'kb_get_all', 'kb_get_context', or 'kb_update_projects'. The purpose remains unclear beyond the obvious from the name.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines1/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. There are multiple sibling tools that might retrieve project-related information (e.g., 'kb_get_all', 'kb_get_context', 'kb_update_projects'), but the description offers no context, prerequisites, or exclusions to help an agent choose appropriately. This leaves the agent with no usage direction.

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