Skip to main content
Glama
Sign In
jobs-tools-knowledgebase

jobs-tools-knowledgebase

by dbsxortime
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

Jobs-tools-knowledgeBase-deleteUserContext

Delete user context data irreversibly. Clear a specific category like skills or goals, or remove all user context at once.

Instructions

Delete user context data (DANGER: Irreversible)

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "Jobs-tools-knowledgeBase-deleteUserContext"
  }
}

Input Schema

NameRequiredDescriptionDefault
categoryNoSpecific category to delete (skills, interests, goals, personality, workStyle, projects, custom)
clearAllNoClear all user context data

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.14

TDQS

B3.2/5.0
Behavior3/5

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

The description includes a 'DANGER: Irreversible' warning, which is a useful behavioral disclosure. However, with no annotations, it fails to explain the scope of deletion (e.g., what categories cover, whether clearAll wipes everything) or side effects beyond irreversibility.

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, front-loaded sentence with a prominent danger warning. Every word earns its place, achieving maximum conciseness.

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?

Despite full schema coverage, the description is incomplete for a destructive tool with no annotations or output schema. It does not specify behavior when both parameters are provided, what happens with no parameters, or what the return value indicates.

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?

Schema description coverage is 100%, so the schema already fully documents both parameters with descriptions. The tool description adds no additional semantic meaning beyond what the schema provides.

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 tool deletes user context data with a specific verb and resource. However, it does not explicitly differentiate itself from sibling tools like deleteUserContextItem, which deletes a single item rather than a category or all data.

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 such as deleteUserContextItem or resetUserProfile. The only additional information is the danger warning, which is not usage direction.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools