Skip to main content
Glama

kb_get_personal

Retrieve stored personal details and preferences to provide AI assistants with immediate context about you, enabling personalized interactions across sessions.

Instructions

Get personal information

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • Tool handler in the main switch statement that calls KnowledgeManager.getPersonal() and returns the result as JSON-formatted text content.
    case 'kb_get_personal': {
      return {
        content: [
          {
            type: 'text',
            text: JSON.stringify(km.getPersonal(), null, 2)
          }
        ]
      };
    }
  • Tool schema definition in the tools array, specifying name, description, and empty input schema.
    {
      name: 'kb_get_personal',
      description: 'Get personal information',
      inputSchema: {
        type: 'object',
        properties: {}
      }
    },
  • Implementation of getPersonal() method in KnowledgeManager class, which returns a shallow copy of the personal info from the knowledge base.
    getPersonal(): PersonalInfo {
      return { ...this.kb.personal };
    }
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. 'Get' implies a read operation, but it doesn't specify if this requires authentication, has rate limits, returns structured data, or what happens on failure. For a tool with zero annotation coverage, this is inadequate as it misses key behavioral traits.

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

Conciseness3/5

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

The description is extremely concise ('Get personal information'), which could be seen as efficient. However, it's under-specified rather than appropriately sized—it lacks necessary details like what 'personal information' entails. It's front-loaded but doesn't earn its place with meaningful content, making it borderline between concise and incomplete.

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 tool's purpose (retrieving personal information), no annotations, no output schema, and 0 parameters, the description is incomplete. It doesn't explain what 'personal information' includes, the return format, or any behavioral context. For a tool in a knowledge base context with siblings like 'kb_update_personal', more detail is needed to be fully helpful.

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 lack of inputs. The description doesn't add parameter details, but with no parameters, the baseline is 4 as it doesn't need to compensate for schema gaps. It implicitly suggests no inputs are required, which aligns with the schema.

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 personal information' is a tautology that essentially restates the tool name 'kb_get_personal'. It doesn't specify what type of personal information (e.g., contact details, preferences, identification) or from what source. While it distinguishes from siblings like 'kb_get_professional' by mentioning 'personal', it lacks the specific verb+resource clarity needed for a higher 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?

There is no guidance on when to use this tool versus alternatives. It doesn't mention prerequisites, context (e.g., after initialization), or compare to siblings like 'kb_get_all' or 'kb_get_preferences'. The description provides no usage context, leaving the agent to infer based on the name alone.

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